I like that way too
On Tue, Oct 28, 2008 at 9:02 PM, Karsten Dambekalns <[EMAIL PROTECTED]> wrote:
> Hi.
>
> Stan Vassilev | FM wrote:
>>
>> A yet another compromise is possible as the lesser evil:
>
> ...
>>
>> They key change is: not to make difference between internal and user
>> global functi
Hi.
Stan Vassilev | FM wrote:
A yet another compromise is possible as the lesser evil:
...
They key change is: not to make difference between internal and user
global functions, just fall back to global ones, so that there's no
additional confusion among drop-in replacements, user resources,
History has shown
us that breaking code (e.g. PHP4 - PHP5) slows adoption of new
versions.
Bad example as PHP4 > 5 broke existing code. No existing code has namespaces
in it. Anyway:
A yet another compromise is possible as the lesser evil:
Resolution for classes:
namespace
I totally agree with Josh, same argument - resolving to global resources
should be by default, so we don't need to rewrite a lot of code, witch we
want to namespace. Namespaced functions will be called far less in code then
global ones.
2008/10/28 Josh <[EMAIL PROTECTED]>
> Hey,
>
> I think that
Hey,
I think that using \ to prefix global symbols in namespaces would be
quite dumb. It would feel counter-intuitive because then if your
coding you would need to think to yourself, "am I in a namespace?",
thus increasing the chance for simple errors. It would be incedibly
annoying when writing p
