> right, and it's "easier" isn't good practice (as anyone who has to maintainI am for adding those tags by the way for clarity, but I didn't like the way it was done, and I am not in favor of such mass commits, especially in cases where the target of the commit is not critical, it can be easily overcome in the processing system...
Hell no, tags should be there in the scripts, this has nothing to do with the processing system. PHP code *requires* tags, so they should go into the examples.
I agree completely. Hacking up the processor because we didn't do something
> old, poorly written code can attest).
First of all, some of the examples imply some context (like an opened database connection), and only present a part of a php script. Therefore adding PHP tags can be misleading.
Second maintaining some compatibility code in the processing system is much easier to handle, than giving more hours to work to dozens of translators, just because this method seems to be cleaner. Or are you confident, noone really cares about the diffs? Then why do we have those translation CVS modules??
Goba
-- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
