...this probably goes to IOhannes, but maybe someone else knows?
...I'm adding some new wrappers to the opengl stuff, and have come across a call that seems to take more than 4 args:
void ProgramEnvParameter4dARB(enum target, uint index, double x, double y, double z, double w);
...CPPExtern.h only defines up to CPPEXTERN_NEW_WITH_FOUR_ARGS, so do I just need to add some more macros?
l8r, james
James Tittle II wrote:
...CPPExtern.h only defines up to CPPEXTERN_NEW_WITH_FOUR_ARGS, so do I just need to add some more macros?
pd only allows you to set a maximum of 5 typechecked arguments. why gem goes only till 4, i don't know. however, i think it might be simpler to use CPPEXTERN_NEW_WITH_GIMME and do a "manual" type-checking.
(otoh, it should be rather simple, to add another macro to CPPExtern.h)
mfg.asd.r IOhannes
On Oct 11, 2004, at 5:21 PM, zmoelnig@iem.at wrote:
James Tittle II wrote:
...CPPExtern.h only defines up to CPPEXTERN_NEW_WITH_FOUR_ARGS, so do I just need to add some more macros?
pd only allows you to set a maximum of 5 typechecked arguments. why gem goes only till 4, i don't know. however, i think it might be simpler to use CPPEXTERN_NEW_WITH_GIMME and do a "manual" type-checking.
(otoh, it should be rather simple, to add another macro to CPPExtern.h)
ok, so I may be a little "dense" due to decompression from the flight, but I need a bit more explanation of the differences between CPPEXTERN_NEW_WITH_GIMME and *_WITH_ARGS: what did you mean by "manual" type-checking? I've been looking at the different usages throughout the other code, but it seems to be somewhat differently used in each circumstance...
...If pd only allows 5 typechecked arguments, does that mean I can't make a CPPEXTERN_NEW_WITH_SIX_ARGS?
...If I use the GIMME method, does that limit the number of inlets I can deal with? Fr'instance, for this current wrapper "GEMglProgramEnvParameter4dARB", I'd like to have seperate inlets for not only target and index, but also x, y, z, w: after all, there is another call "GEMglProgramEnvParameter4dvARB" that would accept target, index, and a vector of x,y,z,w (and therefore only need 3 inlets)...I ask this because it seems that some GIMME-based externs use a "params" message, and I don't want to require non-vector accepting GL calls to accept vectors...
thanx, james
James Tittle II wrote:
CPPEXTERN_NEW_WITH_GIMME and *_WITH_ARGS: what did you mean by "manual" type-checking? I've been looking at the different usages throughout the
this means, you have to check the types of the atoms, whether they fit your assumption, if you want to make sure, that the "correct" arguments are supplied by the user. if someone types [GEMglProgramEnvParamter4dARB foo bar 1 2 3] it is your responsibility to tell the user, that this won't work.
...If pd only allows 5 typechecked arguments, does that mean I can't make a CPPEXTERN_NEW_WITH_SIX_ARGS?
exactly.
"typechecked" means, that pd checks the correct types for you, and if the arguments won't fit in, creation of the object is denied.
with c-externals one could always return a NULL-pointer when the manual typecheck fails, however this is not possible in C++ (we could try to utilize some exception that is thrown when creation fails...)
...If I use the GIMME method, does that limit the number of inlets I can deal with? Fr'instance, for this current wrapper "GEMglProgramEnvParameter4dARB", I'd like to have seperate inlets for not only target and index, but also x, y, z, w: after all, there is another call "GEMglProgramEnvParameter4dvARB" that would accept target, index, and a vector of x,y,z,w (and therefore only need 3 inlets)...I ask this because it seems that some GIMME-based externs use a "params" message, and I don't want to require non-vector accepting GL calls to accept vectors...
no, there is no relationship between the number of type-punned (oh another word!) inlets and the nunber of (type-checked) arguments.
probably it would be easiest, to not use any arguments at all and supply all parameters via inlets.
mfg.as.dr IOhannes
-
James Tittle II -
Johannes M Zmoelnig -
zmoelnig＠iem.at