Rasmus Lerdorf wrote:
I think you are again becoming a victim of too much generalization.
Like using the slower re-entrant mysql client library, for example, just
in case you have a threaded SAPI that needs it. 99% of people are going
to be using the prefork Apache SAPI or fastcgi, neither
Patrick ALLAERT wrote:
2010/1/13 Derick Rethans der...@php.net:
On Tue, 12 Jan 2010, Raphael Geissert wrote:
[snip]
Would it be possible to force short_open_tag to a specific value for
those applications alone? Perhaps through an .htaccess file? That way,
Debian keeps the PHP default
Raphael Geissert wrote:
Patrick ALLAERT wrote:
2010/1/13 Derick Rethans der...@php.net:
On Tue, 12 Jan 2010, Raphael Geissert wrote:
[snip]
Would it be possible to force short_open_tag to a specific value for
those applications alone? Perhaps through an .htaccess file? That way,
Debian
Hi,
and why Debian still use the php module version by default ?
By using the fcgi version each application can have it's own php.ini.
Furthermore, it's a different problem but this will also allow use of a
specific unix account for each apps.
In the actual Debian's php.ini we can found about
Raphael Geissert wrote:
Rasmus Lerdorf wrote:
But why do you want them to change? Short tags are convenient and if
the app doesn't have to worry about ?xml or ?xsl type stuff, it can
run happily with short tags enabled.
Because it is just not about the application but the whole
Rasmus Lerdorf wrote:
Then we have to have logic to differentiate ? from ?xml, for example.
It would make the parser quite a bit more complex if we have to start
parsing stuff outside of the active open tags. Not sure it is worth the
effort nor the extra overhead.
Isn't something
Raphael Geissert wrote:
I'm still looking for a way to warn about the use of open_short_tag not
being explicitly enabled on the PERDIR level. Otherwise the only thing I see
would make applications change would be when the default is Off and they
break.
But why do you want them to change?
Raphael Geissert wrote:
Rasmus Lerdorf wrote:
Raphael Geissert wrote:
I'm still looking for a way to warn about the use of open_short_tag not
being explicitly enabled on the PERDIR level. Otherwise the only thing I
see would make applications change would be when the default is Off and
2010/1/13 Derick Rethans der...@php.net:
On Tue, 12 Jan 2010, Raphael Geissert wrote:
[snip]
Would it be possible to force short_open_tag to a specific value for
those applications alone? Perhaps through an .htaccess file? That way,
Debian keeps the PHP default but still allows those apps to
On Tue, 12 Jan 2010, Raphael Geissert wrote:
As mentioned on my other post, at Debian we are planning to include
5.3 in Squeeze. Given that the development and production php.ini
files both turn short_open_tag by default but many applications
shipped by Debian itself still require it to be
Rasmus Lerdorf wrote:
Raphael Geissert wrote:
However, we would like to contribute in the quest to make applications
stop using short_open_tag. To do so, we have decided to throw an
E_DEPRECATED warning when an application makes use of short_open_tag. The
current implementation can be found
Raphael Geissert wrote:
Rasmus Lerdorf wrote:
Raphael Geissert wrote:
However, we would like to contribute in the quest to make applications
stop using short_open_tag. To do so, we have decided to throw an
E_DEPRECATED warning when an application makes use of short_open_tag. The
current
Raphael Geissert wrote:
However, we would like to contribute in the quest to make applications stop
using short_open_tag. To do so, we have decided to throw an E_DEPRECATED
warning when an application makes use of short_open_tag. The current
implementation can be found at [1].
How does
13 matches
Mail list logo
