Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-18 Thread Raphael Geissert
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, neit

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-16 Thread Rasmus Lerdorf
Raphael Geissert wrote: > Patrick ALLAERT wrote: > >> 2010/1/13 Derick Rethans : >>> 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, >>> Deb

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-16 Thread Raphael Geissert
Patrick ALLAERT wrote: > 2010/1/13 Derick Rethans : >> 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

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-15 Thread Ángel González
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 > run happily with short tags enabled. >> > > Because it is just not about the application but the whole system. With the > apac

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-15 Thread Olivier B.
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

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-14 Thread Patrick ALLAERT
2010/1/13 Derick Rethans : > 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 work. R

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-14 Thread Rasmus Lerdorf
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

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-14 Thread Raphael Geissert
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 >> they break. > > But

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-14 Thread Rasmus Lerdorf
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

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-14 Thread Raphael Geissert
Rasmus Lerdorf wrote: > > Then we have to have logic to differentiate 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 similar already done? I was

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-13 Thread Rasmus Lerdorf
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

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-13 Thread Raphael Geissert
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 b

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-13 Thread Derick Rethans
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

Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-12 Thread Rasmus Lerdorf
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 d

[PHP-DEV] Throwing an E_DEPRECATED for short_open_tag

2010-01-12 Thread Raphael Geissert
Hi again, Disclaimer: although discussions about this topic tend to be heated (and hated) this is not the usual short_open_tag thread. Please refrain from talking about other previous proposals and whether short_open_tag should be dropped or not. As mentioned on my other post, at Debian we are