Yes they are *exactly* the same types of problem.
I still haven't captured the error message, and based on this I don't think I need to.
My 2 cents:
I agree that returning an empty string and returning a "None" object are fundamentally different.
However that seemed like an easy way to work around the problem involving a "const char **".
I would pose this hypothetical situation:
What if you have a function that returns three object pointers of the same type?
If the function tries to return (None, "some pointer", None), how does the Python script know
which one was just returned?
It almost doesn't look like there is an easy answer here.
Marshall
--- Karl Fogel <kfogel@newton.ch.collab.net> wrote:
> Marshall White <cscidork@yahoo.com> writes:
> > In Python, calling a function that has more than one output goes something like this:
> > out1, out2, out3 = foo()
> >
> > The error said something to the effect of "there are more variables
> > than the number of 'things' returned from the function." Of course
> > the actual error message didn't use those words exactly, but that
> > was what "my interpretation."
> >
> > The error was easy enough to reproduce. I'll revert, rebuild and
> > get back to you with the exact error message.
>
> The error you're describing is *exactly* the problem that necessitated
> the workaround in revision 5137. See my mail just now, with the
> subject
>
> "inconsistency in Python SWIG return parameters"
>
> Does it seem familiar?
>
> -K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 27 23:45:17 2003