Re: short_open_tag

> For somebody who never uses/has used XML, it's incomprehensible, why > he/she has to type 3 extra chars every time. Thats just bloody mindedness / lazyness ... or do we actively encourage sloppy code? > IF (major if) anything, make a config-option "--enable-xml-compliance" > which checks/corrects a number of things (like, check apache > symbols/disable short tags/enable > related modules/add <?xml tag at start of doc output). This would need to be an overridable ini setting rather than a config option as many dont have access to the config line to either turn it on or off. Thats left to the hoster. > Another -1, because it's a security risk, as your (legacy) sources will > be sent to the client, > if you're not aware of this. This may expose passwords, internal > networks and what not. The security risk there is the developer for having sensative information in a publicly accessable file. The same could be said for putting .php3 files onto a PHP4 enabled apache installation - which on a default install of PHP and Apache doesnt parse .php3 files and thus outputs them in the same manner. Dont forget, not all servers have short_open_tag's enabled - your "security risk" (aka bad coding) is ever present there also. I am still +1 on some how getting away from short_open_tag support, if nothing else, to encourage better coding practices (just as we did with turning register_globals off by default). -- Dan Hardiker [dhardiker@staff.firstcreative.net] ADAM Software & Systems Engineer First Creative