Vote from a "Mere User"

I am a "mere user" you can consider as well. I usually just read
internals. I wanted to add input into the namespace issue.

Using a difference of ::: or :: for separators is really confusing. I
could slip up in programing by missing a single : and then have to go
back to debug and it would be very easy to miss this.
I don't think option 1 and 2 would work here unless we used a
different separator. At this time I do not have a suggestion for a
separator. My eye sight isn't all that perfect, in fact typing them in
this message, I had to double check I typed them correctly. Although
this solves it, this isn't very user friendly.

Option 3 sounds nice, but since reading a previous internals note, you
can use these in a if/else statement. Which I would prefer almost for
those weird cases where you need to only include a class if it was for
something specific such as a database, operating system or php version
compatibility.

The issue I see with number 4 is lets say I have a forum and a cms. If
I wanted to bridge those two and they had this conflict, I wouldn't be
able to bridge these two very easily now. Conflicting code while
working with apis and other open source/free scripts is my only
concern with this.

That said, I think option 3 would work the best here with option 1 as
another choice if we used a different separator that was more unique.

Jeremy

A "mere user" here too with some php namespace experience (with
current
implementation).

Issue 1: Choice #4, with a fallback on choice #3

Issue 2: This should be a php.ini option, typically it's going to
cause
a lot of (useless) calls to __autoload() for some existing code while
migrating to a namespace-oriented code.
This is also going to break things for some people who use require()
in
__autoload().

Mark

Le vendredi 17 octobre 2008 à 13:18 +1030, Josh a écrit :

I'm another "mere user", but here are my votes

Issue 1: Choice #3

Issue 2: Agree with Greg.

Josh Heidenreich
ZCE