Pete Robbins wrote:
On 25/06/07, Caroline Maynard <[EMAIL PROTECTED]> wrote:
A fair amount actually, but I am making an assumption that once the
changes are in place, the migration effort will be largely refactoring.
That is, that the non-spec function will resurface in Tuscany
implementation classes (if not adopted by the spec). If this is not the
case, then the response from the php implementation could be different.
Do you have a list of the non-spec interfaces PHP is using? I believe the
getUserData interfaces were added for PHP use??
Yes, the UserData stuff was added as somewhere for consumers (like PHP)
to be able to augment the DataObject with their own data, and it's
crucial to our implementation.
I've given some thought as to how we could easily create a definitive
list of the Tuscany APIs employed. But since the PHP implementation
includes the Tuscany code, we don't have the ability to simply list the
external references as we would for a dynamic library, unless you can
suggest another way.
However we don't have a huge amount of code, and it is very simple to
download it from cvs using
pserver:[EMAIL PROTECTED]:/repository checkout pecl/sdo
and load it into cscope or similar, so you could easily check for
references that way. Or you could just mail us :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
