[Swig-devel] Re: PHP vector problems

[Olly B. <ol...@su...>]

On 2006-02-13, Kevin Ruland <kr...@ku...> wrote:
> Although it is unsightly, I didn't think having the methods named both
> ways really posed a serious problem.

I guess so.  This could be regarded as a feature actually, since it
allows code written for the "-noproxy" bindings to work if proxy classes
are enabled.  That'll be handy for Xapian if/when we switch away from
using -noproxy.

The only way I can see it being a problem is if "class_methodname"
clashed with another wrapped function and overloading resolution
didn't help, which seems fairly unlikely.

Incidentally, the reason we're still using -noproxy at the moment
is that PHP5 doesn't work without it and it seems desirable to keep
the PHP wrappers consistent between PHP4 and PHP5 where possible.

What is involved in adding proxy class support for PHP5?

I had a look aroung (using Google) for documentation for the internals
of PHP5, but there doesn't seem to be much (I've not found very much for
PHP4 either for that matter).  Is there a good reference somewhere I've
missed?

> I thought the problem was related to overloading and argument
> defaulting in constructors (and other class member functions).  I
> fixed this problem in 1.3.28.  If you look closely the method
> "stringvector" is defined twice in addition to the "new_stringvector".

OK, I understand now.

Cheers,
    Olly