Bug #10743: class functions & PHP core functions inconsistently clash ;)

From: Date: Wed, 09 May 2001 07:42:00 +0000
Subject: Bug #10743: class functions & PHP core functions inconsistently clash ;)
Groups: php.dev 
Request: Send a blank email to php-dev+get-54468@lists.php.net to get a copy of this message
From: jjones@net-conex.com Operating system: Linux PHP version: 4.0.4pl1 PHP Bug Type: Scripting Engine problem Bug description: class functions & PHP core functions inconsistently clash ;) Okay.. this has been bugging me for a while.. consider the following: class test { function mail () { print ("Bah\n"); } function fopen () { print ("Bah\n"); } function new () { print ("Bah\n"); } function list () { print ("Bah\n"); } } $temp = new test; $temp->mail(); etc, etc.. This will generate a parse error (expecting `T_STRING') until the new() and list() functions are removed from the class. mail() and fopen() will work. Now.. my question is why the inconsistency? Is there some super-secret reasoning behind not letting me name my classes' objects the same as only a few predefined functions? I'm lazy.. you guys took all the good function names.. why must you tease me with them?! -- Edit Bug report at: http://bugs.php.net/?id=10743&edit=1

« previous php.dev (#54468) next »