marius popa wrote: >> 1. Break every single PHP script that is currently in existence. > maybe an legacy mode can be included in ini
we want less of such legacy mode options, not more plus this would have to be configured per application and not just per server >> 2. Break syntax highlighting (and probably other tools/functions) for >> every IDE that is currently in existence. > this can be fixed by each ide , I talk about something like sure it can be fixed, but you missed the *every* part plus IDEs, editors, highlight tools etc. would have to support both old and new for quite a while >> I'm not sure that much more needs to be said. > I can give another practical example in wxjscript > from this javascript example that can be run on apache server you can see > that is simpler to read and to learn at least for an beginner > http://www.wxjavascript.net/mysql/index.html so instead of clearly marking variables with $ as such there they need to be declared with 'var' instead, and '->' is replaced by '.' ... ... i don't see much of a difference there from a learning point of view though > What i want to say is that php must go forward and yes you can > change/break things in the engine > like in the php 4 to php 5 migration or php5 to php6 sure we can break things if there is a compelling reason to do so, i'm just totally missing the compelling part here ... -- Hartmut Holzgraefe, MySQL Regional Support Manager EMEA Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB161028 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
