Andi Gutmans wrote:
Hmm I don't quite understand what bad code vs. good code plays here.
Wordpress is one of the most popular applications out there so it's got
huge value to our community. I bet there's a huge amount of PHP
applications who's source code is of the same quality or worse. Anyway,
the issues I have seen would also be relevant to what you call "good"
code but again, when it comes to compatibility, I don't quite know why
that will play a big role.
Bad good in the sense its messy. But what I was going at is that I find
your proposed list good with the exception of SugarCRM. It might be good
to also include a php5 only app, so that we have a good idea of how
messy code, fairly procedural, E_STRICT complaint etc code ports to PHP6
unicode==off.
I am talking about porting to both unicode_semantics=off and on. This
will give us a good understanding of the difference of the modes and
where we're at. I bet most people who are voicing their opinions have
actually not tried to write a sizeable application with PHP 6 and also
tried to run an existing one on PHP 6
(unciode_semantics=on). I can also do some performance testing in our
ok .. this makes this quite a large undertaking indeed.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
