String concatenation woun't be affected, because you can't concatenate class definitions like in my example. To concatenate you should use variables or strings/numbers. So I don't see any complications with that.
2008/9/29 Stan Vassilev | FM <[EMAIL PROTECTED]> > > Hi, > > I think we need string concatenation here and there ;) > > Regards, > Stan Vassilev > ----- Original Message ----- > From: Arvids Godjuks > To: Stan Vassilev | FM > Cc: PHP Internals List > Sent: Monday, September 29, 2008 9:19 AM > Subject: Re: [PHP-DEV] solving the namespace conflict issues > betweenfunction/staticmethod class constant/ns constant > > > Maybe just use . as namespace separator. > > MyNameSpace.SomeClass::_getInstance()->SomeDBClass->Query(); > > That will eliminate all resolution problems, it isn't used for anything > than string concatenation, and it's one symbol. It's 100% better than \ and > I think it would be better than ::: or :::: and so on. > A point against \ is that it has special meaning in every programming > language as escape character, so it is 100% bad to use it. >
