Yeah, one of the main reasons for requesting it was that like shanes
sybase class midgard also uses delete as the row deletor, - this doesnt
really affect midgard as the method is defined in the php extension, not
the php, however when I wrote DB_DataObject, and midgard lite, to take
advantage of the same style of database access it was a pretty obvious
method name..
one of the other ones that threw me was that 'list' did not work
either.. (in ZE1 also obviously)..
looking at the code I would guess that you could support most valid
keywords as method names
valid_method_names:
T_STRING
| T_DELETE
| T_LIST
| T_NEW
the reasoning for not supporting all keywords?
- user getting confused and accedentily using a keyword rather than the
method
on the code side I cant see any major obsticales to supporting them.. -
or did I miss something.. - the above code would add very little
slowdown to the parser - especially as I assume it matches the first on
the list anyway..
I did see it mentioned as a critisium that there where alot of reserved
words that made defining class methods painfull ( I dont totally agree
with that, but it would put it to bed)
regards
alan
Andi Gutmans wrote:
> Alan,
>
> There was a discussion about this a long time ago and it was decided
> not to support this.
> The main reasoning behind this is that we don't want to start
> supporting all other reserved words.
> It's one of the things you'll need to cope with when moving to the
> Engine 2 but a very simple search&replace on your project should do
> the trick.
>
> Thanks anyway,
> Andi
>
>>
>>
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
