Re: SWIG Again

John Lenz <lenz@cs.wisc.edu> writes:

> I keep trying to repeat this, but no one seems to get it. So you will have
> to pardon my shouting.
> THERE IS NO MORE ABI ANYMORE
> let me repeat that
> THERE IS NO MORE ABI ANYMORE

I remember your previous email about the removal of the run-time
library. It sounded like an improvement[1].

That doesn't alter the fact that we write C code to support SWIG, in
swigutil_py.c. That API/ABI has changed in the past, and that API/ABI
is still there. Your patch makes further changes to that C code, and
as I understand it SWIG is in development and provides no guarantees
that 1.3.25 will be API/ABI compatible 1.3.24. Has the SWIG project
changed it's position?

[1] Although as I recall there was something about communication via a
global python variable. If I mix 1.3.X and 1.3.Y will it always work
or is it possible that I will I get a runtime python error?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org