Comments on: Is PHP 5.3 Terminal? Well, It’s Getting One For Namespaces

By: zend_idiots

zend_idiots — Sat, 27 Aug 2011 07:14:35 +0000

I agree with ‘i_ate_god’. Using the backslash is without doubt the stupidest thing I’ve seen. It looks fucking ugly, difficult to read. I’m off to the Python camp.. bye bye Zend and PHP.

By: Jero

Jero — Sat, 24 Jul 2010 01:54:58 +0000

It would seem the example code got scrubbed from my previous comment. Bugger. Let’s have another try:

Solution: Disallow classes with the same name as namespaces. (Like in java, but not exactly. Just use the same namespace (pardon) for namespaces and classes)

IE:
//File1.php
namespace foo;
function bar()
{
return “Broken”;
}
//File2.php
class foo
{
public static function bar()
{
return “Damaged”;
}
}
//index.php
include “file1.php”; //A-Ok!
include “file2.php”; //Fatal Error: Cannot redeclare namespace (foo) with class

echo foo::bar(); //Should have failed before getting here.
//In php 5.3.0, will output “Damaged”
//End IE

This should be simple to implement, and not risk the ire of the community! :D

By: Jero

Jero — Sat, 24 Jul 2010 01:52:21 +0000

Solution: Disallow classes with the same name as namespaces. (Like in java, but not exactly. Just use the same namespace (pardon) for namespaces and classes)

IE:
//File1.php

//File2.php

//index.php

//End IE

This should be simple to implement, and not risk the ire of the community! :D

By: James Irwin

James Irwin — Wed, 12 Nov 2008 23:00:53 +0000

I agree with your “I feel that throwing an error (or warning and choosing one) whenever that situation arises would be a perfectly acceptable solution.” as a way to determine whether A::B is function B in namespace A or method B in class A in case there are both.

By: i_ate_god

i_ate_god — Tue, 28 Oct 2008 20:16:11 +0000

\ is for escape characters. No one uses it for anything else, anywhere.

namespace budgets;

class nightlyTasks;

budgets\nightlyTasks::staticMethod();

Are they fucking stupid or are they fucking stupid? I’ve been using PHP for a long time now, and this is the dumbest thing they’ve done to date.

The justifications for it hold about the same amount of weight as well, nothing. Nothing at all. There is no valid, logical, reasonable justification for having the BACKSLASH as a separator. It will confuse text processors, it will confuse windows users, and it will confuse anyone who has to use PHP after using another language.

Namespace::class::staticMethod()

There is no ambiguity there at all, none. You know what it all is.

Time to take a serious look at Ruby now.