Re: Namespaces bug
| From: | George Schlossnagle | Date: | Wed, 26 Mar 2003 19:39:55 +0000 |
| Subject: | Re: Namespaces bug | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-347@lists.php.net to get a copy of this message | ||
On Wednesday, March 26, 2003, at 02:36 PM, Rasmus Lerdorf wrote:
On Wed, 26 Mar 2003, Shane Caraveo wrote:I think that the argument is that it would be best to disallow it both places, but doing so would break bc for functions. Two wrongs don't make a right, though. Just because there have been confusing syntax choices in the past doesn't mean they should be propagated into the future.Rasmus Lerdorf wrote:I'm not arguing that it is correct, I am simply saying that it is exactly the same issue and it doesn't make a whole lot of sense to me to disallow it for namespaces, but allow it for functions.Couldn't you make the same argument for: function A() {I would :) The syntax is meaningless and confusing if the program does not operate the way it is written. By all sensible considerations, B should be local to A. Since it is not, the syntax should cause a parser error, and the same with namespaces. And then what happens with that stuff when, at some point in the future, proper scoping is implemented?function B() { }}