Re: Deprecate PHP's short open tags, again

> This discussion has gone out of sanity levels the moment people started to state that short > tags is one (of the many) > things PHP has why new programmers and companies don't pick the language or why colleagues > laugh at you and is a > blocker of new bright future etc. and now in this moment this is a do or die situation > otherways next year everyone > will be writing in javascript. No one said that (except you). But current reaction for this RFC could be depressing. I'm using PHP for quite a long time and I really hoped that someday we'll be able to get rid of all (or at least the most of them) the traps and annoying little things from the old days. That doesn't sound realistic anymore... > Except there are 4-5 functions which do the same not to mention `` backtick syntax (can't > there be an accident mixing those with single quotes?). I was talking about all these functions that allows to execute shell commands. What is the point of disabling only one of them? I thought that the problem is in functionality, not in the name :P >> <? $dbPasword = 'my$ecret' ?> is intended >> usage of short open tags. > > On this I could also say that recommendations are to store all credentials outside webroot, I'm afraid you don't understand the problem. Having such code outside of webroot does not help you much if this file will be included from another file (which uses <?php, so it will work as expected). And exposing DB password is just the simplest example - single non-working if can lead to a wide range of bugs with serious consequences, far beyond code leak. Regards, Robert Korulczyk