note 10720 rejected and deleted from Classes and Objects by zak
| From: | zak@php.net | Date: | Thu, 18 Jan 2001 21:54:39 +0000 |
| Subject: | note 10720 rejected and deleted from Classes and Objects by zak | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-9943@lists.php.net to get a copy of this message | ||
In response to the Editor's note to the note dated 01-Nov-2000 from eggbird@bigfoot.com:
Yes, there is an inherent ambiguity when resolving $var->foo->bar. The reason other languages
can support resolving such constructs, however, is that they define an associativity and precedence
to the -> operator as part of the language, just as one defines an associativity and precedence
for inherently ambiguous operators like "+", "*", and "%".
To the language designers: stop ducking the problem by stating there's an ambiguity - resolve
the ambiguity by specification. Improve the language.
My vote? Do the sensible thing and have $member->foo->bar resolve to "the bar member of
the object given by the foo member of the object referenced by $member".