Re: Dropping requirement for `function` keyword for methods in classes/interfaces/etc

While I'm thinking about this (though I should leave it alone): who's to say that PHP won't some day get inner classes? By deciding the "default" inner member of a class will be a function, you're choosing the one that has a global/procedural equivalent where the short syntax won't work, instead of leaving the concept unused for the possible future when: class myClass { mySomething { // is equivalent to class mySomething { (Yes, you could say mySomething(...) { } is a public function and mySomething { } is an innner class, but you get the idea.) -- S.