On Wed, April 18, 2012 9:42 pm, Rasmus Schultz wrote: >> On 04/10/2012 06:20 PM, Adir Kuhn wrote: >> >> "PHP Gotchas, how they came to be, and why we can't simply fix >> them" >> > > can't or won't? > > It seems that the requirement for backward compatibility, as with most > software, stands in the way of any substantial leaps, and makes it > impossible to do away with outdated cruft. As a result, PHP is > dragging around a lot of baggage - both the language itself and the > libraries. > > Hey, here's a crazy thought: > > <?php6 > > Now you don't have to be backward compatible - the bytecode needs to > remain compatible with bytecode generated by standard <?php tags of > course, but you're free to change/improve/deprecate/extend the syntax, > update inconsistent APIs, etc. > > I know this is no small thing, heh. I'm sure there's some technical > reason this isn't even feasible or possible... > > I just figured I'd bring it up anyway, it's always fun to see your > reactions to such radical ideas - bring on the flames! ;-)
Using the Duck Rule, this seems the same as a php.ini switch for core PHP. We all know how that one worked out... -- brain cancer update: http://richardlynch.blogspot.com/search/label/brain%20tumor Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
