Re: reserved word alert

On 8/16/07, Marcus Boerger <helly@php.net> wrote: > Hello Lukas, > > this is a no issue. Prefix your code and be done! > That means prefixing your methods as well ? The problem is when one calls something like a method "import()" You prefix your functions ? I think this is silly. Prefix the class to make it namespace** like, but not the methods... PEAR_ClassName { public static function __PEAR_construct() { } public static function PEAR_import() { } public static function PEAR_export() { } } Which ends in PEAR_ClassName::PEAR_Import(); Whereas: PEAR_ClassName::import(); would usually be ok to do. Prefixing the methods imho is the no go in this case. > marcus > > Wednesday, August 15, 2007, 3:37:20 PM, you wrote: > > > Hi, > > > Someone in the Doctrine channel just brought up the issue of having to > > look forward to ensure mid term compatibility when choosing names for > > identifiers. I guess with namespaces and other things will add new > > reserved words. I think we should have a prominent place on php.net with > > early warning for reserved words that will be in future php releases. > > > regards, > > Lukas > > > > > Best regards, > Marcus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18