Re: POSIX regex

Am 19.07.2007, 14:27 Uhr, schrieb Keryx Web <webmaster@keryx.se>: > Zeev Suraski wrote: > > > Other than the theological views some people on this list have > (either very pro-BC or anti-BC), what did keeping BC cost us? > > Hey that must be me he is talking about - as I am a real theologian! > > So for a theologians 2c on Unicode: > > 1. Teaching unicode and PHP > > As stated elsewhere I am *working* as a teacher. I follow this list for > one *main* purpose and that is I am trying to remedy the extremely sad > situation when it comes to books and other teaching material about PHP > in Sweden. All books we have got by Swedish authors are so bad that I > actively discourage people from reading it! > In german books and howtos (the biggest non-english PHP-comunity I think) there was at the release of PHP5 the same, that books who claims to teach the new PHP5 style, in reality only add one or two capters of specific OO matters and the rest was PHP4 only. The introduction to the OO-programming was also only in php4-style. I think this should be handled stricter by the PHP-developers. Code-practices, php.ini-setting, function or similar that are not wanted by the php-developers or not save to use should be collected on a seperate site (badcode.php.net or so) and make clear, why this is bad-code. Everyone how whant's to publish a book, make howto or want to teach php have to follow this guide. If someone who doesn't care about this guide wouldn't be allowed to use PHP (which is copyrighted I think) for there publications and probatly make money with teaching or writing books for PHP. This should be a adition for the php-licence I think. This would be a big sign for all who uses php which is totaly unwanted from the php-developers. This could also be a clearly coverage of BC-breaks. Ps: Normaly I'm only reading and not posting to this list as a PHP-scripter to stay in touch with the newest developments of php, but this time I has give my 2€cents to this topic. -- MFG Wolfgang Stelzhammer