El grupo al cual envías entradas es un grupo Usenet. Si envías mensajes a este grupo, cualquier usuario de Internet podrá ver tu dirección de correo electrónico
I've posted the solution for one of them, but for the set_magic_quotes_runtime() error I don't know the solution. In the case of split() I think it can be easily replaced by explode(), at least in that case, not in all of them.
> I've posted the solution for one of them, but for the
> set_magic_quotes_runtime() error I don't know the solution. In the
> case of split() I think it can be easily replaced by explode(), at
> least in that case, not in all of them.
> Thanks,
> Alvaro
-- Jonathan H. Wage (+1 415 992 5468)
Open Source Software Developer & Evangelist
sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
You can contact Jonathan about Doctrine, Symfony and Open-Source or for
training, consulting, application development, or business related questions
at jonathan.w...@sensio.com
The other solution I may find, to be able to get those performance
improvements of PHP 5.3, is to remove the E_DEPRECATED reporting,
which I won't like to have to do that.
Anyway, It would be nice if those bugs get fixed :)
> I've posted the solution for one of them, but for the
> set_magic_quotes_runtime() error I don't know the solution. In the
> case of split() I think it can be easily replaced by explode(), at
> least in that case, not in all of them.
> Thanks,
> Alvaro
> -- > Jonathan H. Wage (+1 415 992 5468)
> Open Source Software Developer & Evangelist
> sensiolabs.com | jwage.com | doctrine-project.org | symfony- > project.org
> You can contact Jonathan about Doctrine, Symfony and Open-Source or
> for training, consulting, application development, or business
> related questions at jonathan.w...@sensio.com
> I've posted the solution for one of them, but for the
> set_magic_quotes_runtime() error I don't know the solution. In the
> case of split() I think it can be easily replaced by explode(), at
> least in that case, not in all of them.
> You can contact Jonathan about Doctrine, Symfony and Open-Source or for > training, consulting, application development, or business related > questions at jonathan.w...@sensio.com <mailto:jonathan.w...@sensio.com>
>> I've posted the solution for one of them, but for the
>> set_magic_quotes_runtime() error I don't know the solution. In the
>> case of split() I think it can be easily replaced by explode(), at
>> least in that case, not in all of them.
>> You can contact Jonathan about Doctrine, Symfony and Open-Source or
>> for
>> training, consulting, application development, or business related
>> questions at jonathan.w...@sensio.com <mailto:jonathan.w...@sensio.com
> The other solution I may find, to be able to get those performance > improvements of PHP 5.3, is to remove the E_DEPRECATED reporting, > which I won't like to have to do that.
> Anyway, It would be nice if those bugs get fixed :)
Just a clarification, these are not bugs. These are warnings that the given functionality may disappear in new major versions (aka PHP 6). As such they serve as a friendly reminder to change the given code in case one plans to upgrade to PHP6. E_DEPRECATED should only be enabled in development and always disabled during production.
>> The other solution I may find, to be able to get those performance
>> improvements of PHP 5.3, is to remove the E_DEPRECATED reporting,
>> which I won't like to have to do that.
>> Anyway, It would be nice if those bugs get fixed :)
> Just a clarification, these are not bugs. These are warnings that the
> given functionality may disappear in new major versions (aka PHP 6).
> As such they serve as a friendly reminder to change the given code in
> case one plans to upgrade to PHP6. E_DEPRECATED should only be enabled
> in development and always disabled during production.
> regards,
> Lukas Kahwe Smith
> m...@pooteeweet.org
> On Tue, Nov 3, 2009 at 7:55 AM, Lukas Kahwe Smith
> <m...@pooteeweet.org> wrote:
>> On 03.11.2009, at 06:35, harryjekyll wrote:
>>> According to the installation page:
>>> PHP >= 5.0
>>> Is supported, which includes 5.3
>>> The other solution I may find, to be able to get those performance
>>> improvements of PHP 5.3, is to remove the E_DEPRECATED reporting,
>>> which I won't like to have to do that.
>>> Anyway, It would be nice if those bugs get fixed :)
>> Just a clarification, these are not bugs. These are warnings that the
>> given functionality may disappear in new major versions (aka PHP 6).
>> As such they serve as a friendly reminder to change the given code in
>> case one plans to upgrade to PHP6. E_DEPRECATED should only be
>> enabled
>> in development and always disabled during production.
>> regards,
>> Lukas Kahwe Smith
>> m...@pooteeweet.org
> On Tue, Nov 3, 2009 at 7:55 AM, Lukas Kahwe Smith
> <m...@pooteeweet.org> wrote:
>> On 03.11.2009, at 06:35, harryjekyll wrote:
>>> According to the installation page:
>>> PHP >= 5.0
>>> Is supported, which includes 5.3
>>> The other solution I may find, to be able to get those performance
>>> improvements of PHP 5.3, is to remove the E_DEPRECATED reporting,
>>> which I won't like to have to do that.
>>> Anyway, It would be nice if those bugs get fixed :)
>> Just a clarification, these are not bugs. These are warnings that the
>> given functionality may disappear in new major versions (aka PHP 6).
>> As such they serve as a friendly reminder to change the given code in
>> case one plans to upgrade to PHP6. E_DEPRECATED should only be
>> enabled
>> in development and always disabled during production.
>> regards,
>> Lukas Kahwe Smith
>> m...@pooteeweet.org
I've checked inside symfony for the string magic_quotes_runtime
I've saw that it appears many times along with
get_magic_quotes_runtime and set_magic_quotes_runtime.
The behavior always is to store in a variable the return of
get_magic_quotes_runtime, then set_magic_quotes_runtime(0) is called
to perform an operation, like read from a file. Once finished,
set_magic_quotes_runtime() is called again to restore the original
value.
Also the default settings in symfony is to set magic_quotes_runtime to
off inside the php.yml file
Except for using symfony in a shared host, I don't see a reason to
keep all that behavior, when a default value of Off or the lack of it (For PHP 5.3) will work.
Anyway, I think this issue is not easy to fix, because it may break
several projects.
As a note apart from symfony, I found the usage of
magic_quotes_runtime in several places on the SWIFT mailer project.
But I'm not sure which version we are using in our projects or if in a
new version of SWIFT those problems are solved.
> On Tue, Nov 3, 2009 at 7:55 AM, Lukas Kahwe Smith
> <m...@pooteeweet.org> wrote:
>> On 03.11.2009, at 06:35, harryjekyll wrote:
>>> According to the installation page:
>>> PHP >= 5.0
>>> Is supported, which includes 5.3
>>> The other solution I may find, to be able to get those performance
>>> improvements of PHP 5.3, is to remove the E_DEPRECATED reporting,
>>> which I won't like to have to do that.
>>> Anyway, It would be nice if those bugs get fixed :)
>> Just a clarification, these are not bugs. These are warnings that the
>> given functionality may disappear in new major versions (aka PHP 6).
>> As such they serve as a friendly reminder to change the given code in
>> case one plans to upgrade to PHP6. E_DEPRECATED should only be
>> enabled
>> in development and always disabled during production.
>> regards,
>> Lukas Kahwe Smith
>> m...@pooteeweet.org
|
