Hi Guilherme, I read your updated RFC: https://wiki.php.net/rfc/abstract_final_class
IMO the RFC as such makes sense now (abstract final confusion is eliminated. In addition to turn methods implicitly into static methods, the __construct of a static class should be implicitly private as well. I am not sure what makes more sense for PHP, but just as thought-provoking impulse, wouldn't it be better just to check that all methods are static and __construct private instead of turning methods magically into static methods and __construct private? And then there is one bit which I do not understand. What do you mean with: "There's no way of adding static variables to a namespace. This would address this issue too." How does this RFC address this problem? Cheers, Robert -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
