Kristian Koehntopp wrote:
On Tuesday 22 October 2002 08:13, Terence Kearns wrote:Ideally this is true, but as so many poeple have pointed out, not every developer has access to the ini file on their ISPs server. Indeed, maintaining a php.ini file is already a nightmare for ISP hosting to unspecified groups PHP users. It's more the *question* of available access that is the problem (and will [apparently] continue to be the problem), not the access itself.
I would hate to see PHP's simple but awsome application producingI can see how short_open_tag enabled makes life harder than it should be
capability essentially *crippled* (or at least stifled) when XML becomes
the norm because inter-application functionality (such as SOAP for only
*one* example) is essential as the web landscape evolves.
for the XML-using PHP-developer. I fail to see how this can happen in a
situation where this developer has no control over the appropriate php.ini
setting, though.
I see where you're coming from but I for one am not arguing for the sake of being a "lean and clean" purist. My main concern is that when XML becomes very popular, trying to implement it will become a "NON-trivial" exercise for the great unwashed. And I agree that PHP always has been a great tool for the great unwashed. I agree that this is one of it's greatest streangths.
My fear is that the oh-so-obvious short-term inconvenience is overshaddowing the more obscured but more profound long-term negative impact on the ease-of-use value in PHP.
At least we're concerned about the same thing ;-)
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
