So does that mean the new NS operator is actually \\ and not \ ? No developer is going to be relying on single \'s -- too likely to become an error in maintenence, and too inconsistent (see strings discussion).
Jevon On Tue, Oct 28, 2008 at 12:11 AM, Arvids Godjuks <[EMAIL PROTECTED]>wrote: > This was argued for months, there was tons of emails to read and backslash > is best for most people. PHP is dynamic language - that makes some major > restrictions, so you just can't apply something that is already in use > easily. That's why :: was rejected in first place. That's why . was > rejected, other separators had other issues. Backslash is easy to see, easy > to type (most layouts have it without Shift or something else) and clearly > says - I'm a namespace! > So anyway - in any language you will find something that you would't like. > You just live with that or chouse another language. That's all. > > 2008/10/27 Thomas Lee <[EMAIL PROTECTED]> > > > Lester Caine wrote: > > > >> The backslash is not ideal, but I think we all need to get behind it > >> rather than complaining. The only other real alternative today is to > shelve > >> namespaces altogether for the next release rather than putting something > in > >> that is simply not practical to extend later? > >> > > I'd prefer to see it shelved for another release with the aim of fixing > > whatever technical barriers made the syntax unworkable in the first > place. > > I'm sure you'd have plenty of volunteers. > > > > My personal concern is that once this goes public, we (the end users) are > > stuck with that decision for the forseeable future. > > > > I think there's obviously enough unhappy campers here that this option > > should be at least considered. Not that I'm holding my breath or > anything. > > > > Everybody seems to be getting awfully emotional about this ... > > > > Cheers, > > > > T > > > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > >
