Hi Damon
thanks for the answer. It's good to know about the genesis of a
decision. It's been so for 10 years and I certainly wouldn't argue a
minute about a decision taken long ago. My problem was simply to have a
wider understanding of the technicalities that lead to the adoption of
<? as start tag, ruling out the existence of some compelling reason for
taking that decision instead of another.
-- Massimo
On 2012-07-25 19:03, Damon Courtney wrote:
It was just the tag that everyone else had sort of arbitrarily
decided was the default. Since Apache wouldn't let you pass any
given
file through more than one handler (by mime type), it wasn't
important
to distinguish it from PHP and others. I suppose we could have made
the parser look for a space after the <? to avoid stuff like this,
but
honestly, it never came up until now. To do so now would break
backward compatibility, even though I doubt many use <? without a
trailing space.
Basically, any answer other than a workaround, at this point, is
going to break backward compatibility. I'm not a fan of that when
there's no good reason and a workaround. We can argue all day about
what SHOULD have been done 10 years ago, and I might even agree with
you, but the point is that it's done now and has been in use for a
decade.
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
