Re: Re: [Implementation] Calling wrapped functions, converters, policies
Daniel Wallin <[email protected]>
| Newsgroups | gmane.comp.lib.boost.langbinding |
|---|---|
| Message-ID | <[email protected]> |
David Abrahams wrote: > Daniel Wallin <[email protected]> writes: > > >>David Abrahams wrote: >> >>>I would be strongly inclined to say that unless you _explicitly_ say >>>otherwise, each C++ argument comes from the Py/Lu argument in the >>>same position. Your example uses implicit argument shifting, which >>>makes me nervous. >> >>Why does it make you nervous? Is there any potential danger in doing >>this that I'm missing? > > > Well, suppose in a 5-arg function you write: > > getC++.arg(2).from_Python_arg(1) > > [Sorry, can't stop inventing syntax ;-)] > > The question is, what happens to to the other 4 arguments? It's far > from obvious to me. Now suppose you add > > , getC++.arg(1).from_Python_arg(4) > > Now it's even less obvious. Sorry, but I can't parse this. :) Could you please elaborate? -- Daniel Wallin ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/