Re: note 10720 added to Classes and Objects
| From: | Zak Greant | Date: | Thu, 18 Jan 2001 21:55:13 +0000 |
| Subject: | Re: note 10720 added to Classes and Objects | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-9941@lists.php.net to get a copy of this message | ||
Hi Rick,
This would be best addressed by making a feature request at bugs.php.net or
posting a message to the developers list (php-dev@lists.php.net).
--zak
----- Original Message -----
From: <rick@eastcore.net>
To: <php-notes@lists.php.net>
Sent: Thursday, January 18, 2001 2:51 PM
Subject: [PHP-NOTES] note 10720 added to Classes and Objects
> 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".
>
> http://www.php.net/manual/en/language.oop.php
>
>
> --
> PHP Notes Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: php-notes-unsubscribe@lists.php.net
> For additional commands, e-mail: php-notes-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>