Re: namespace separator and whining

Steph Fox wrote:

IT will break the code from everybody who doesn'T expect such a flag exists and the average application user won't know and jsut see errors which "randomly" occur.

Erm, how is that going to happen? This is basically a tighter setting that can *optionally* be used and should *always* be used in development. It would be documented loud and clear in the PHP manual, where people go to find out about new/different-from-Java language elements. There's a *possible* slowdown and *possible* conflicts if you never use it, but the people most likely to never use it are those least likely to be loading lots of third-party OO code in the first place.

No ini settings for basic behavior.

Ah well we might as well throw out E_STRICT too! - Steph

I don't think it's going to prevent writing portable code, at least for serious framework developers, because they'll prefix their classes anyway. But I think it's dangerous and will cause unexpected behavior for the average user. This was discussed before, I'm with Stas: Global classes cannot be overriden unless explicitly prefixed. -- Rodrigo Saboya