> Classes always should be declared with class keyword, because there could
> be ambiguity whether it's class, interface or trait.
If only inner classes are allowed in a given PHP version, there's no
ambiguity about whether "something{}" just inside a a class is an
inner class.
That's the justification for removing "function" just inside classes,
isn't it? That it's not ambiguous because the only thing as of PHP.now
that can take the form "sometype somevisibility something(){}" is a
function?
Well, if in PHP.later, the only thing that takes the form "sometype
something{}" is an inner class, then leaving off the "sometype" there
is also unambiguous (but also similarly gratuitous).
And if in PHP.later.still you have inner interfaces, then the
unmodified one still defaults to inner class and only a literal
"interface something{}" is an inner intf.
(I'm attempting a RAA argument but maybe failing....)
-- Sandy | FigureOne Support Team
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
