Nobody wants to turn PHP into Java. But, even if I agree for generics (or templates), I would like to know where is the border line.
Classes, exceptions, interfaces, traits, type hinting in parameters => OK Type hinting in object properties, type hinting of returned values, type templating => KO? Maybe we'd save time if it was clearly defined (and accept my apologies if it was already defined somewhere). 2012/10/21 Stas Malyshev <smalys...@sugarcrm.com> > Hi! > > > Hello, list. I want to propose generics. > > Please no. If you need Java, you know where to find it. Java has a set > of great tools, great books, great community. And it's completely free. > Anybody who needs Java can just do it. I see no need to turn PHP into Java. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
