T_INTERFACE and T_ABSTRACT as valid class names

From: Date: Sat, 20 Oct 2007 13:39:54 +0000
Subject: T_INTERFACE and T_ABSTRACT as valid class names
Groups: php.internals 
Request: Send a blank email to internals+get-32907@lists.php.net to get a copy of this message
Hi, I've already opened a feature request (#43048) but I feel, that there need to be a discussion on that topic. The problem is, that the current pseudo-namespacing used by a huge number of projects (PEAR-style, with underscores and the related file organisation), could not be easily ported to namespaces, as the name "Interface" and "Abstract" is not a valid classname. So something like ... namespace Zend::Db; class Abstract {...} ... will not work. Same for ... namespace Zend::Db::Adapter; interface Interface {...} Nevertheless it would break some syntax highlighting libraries or maybe the tokenizer extension, I would propose to allow at least "Abstract" and "Interface" as a class/interface name. This would make porting to the namespace methodology much easier (I see it quite plainly, a lot of people would develop cripple names like Intrfce or Abstrct just to make the PHP parser happy). cu, Lars

Attachment: [application/pgp-signature] Dies ist ein digital signierter Nachrichtenteil signature.asc
« previous php.internals (#32907) next »