[PHP-DEV] Bug #10910: var $foo = madness

[jjones]

From: [EMAIL PROTECTED]
Operating system: Linux
PHP version:  4.0 Latest CVS (2001-05-16)
PHP Bug Type: Feature/Change Request
Bug description:  var $foo = madness

class foo {
  var $bar = Some string;
  var $baz = new some_other_class_i_defined;
}

I would like for that to work, please.  ;)


-- 
Edit Bug report at: http://bugs.php.net/?id=10910edit=1



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

[PHP-DEV] Bug #10743: class functions PHP core functions inconsistently clash ;)

[jjones]

From: [EMAIL PROTECTED]
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=10743edit=1



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]