Re: [RFC] Deprecate and remove /e modifier from preg_replace
| From: | Reindl Harald | Date: | Sun, 05 Feb 2012 16:34:05 +0000 |
| Subject: | Re: [RFC] Deprecate and remove /e modifier from preg_replace | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-57727@lists.php.net to get a copy of this message | ||
what he hell - if you kill eval you would kill the whole
work of my life and yes i know that eval is evil and
it is only used at one place which is a central and
real important to include modules and set parameters
dynamically
the /e modifier is a total other dimension because it can
be used by people not knowing what they are doing exactly
by C&P any code snippet
eval() is a documentated function
Am 05.02.2012 17:21, schrieb Pierre Joye:
> I think we should remove eval at the same time then. As the risk is
> exactly the same in both situations. Eval is just as evil and can be
> avoided as well (or any other similar features, not sure if other exts
> allow that).
>
> Cheers,
>
> On Sun, Feb 5, 2012 at 3:59 PM, Nikita Popov <nikita.ppv@googlemail.com> wrote:
>> Hi internals!
>>
>> I have written an RFC that proposes to *deprecate* and *remove* the /e modifier:
>>
>> https://wiki.php.net/rfc/remove_preg_replace_eval_modifier
>>
>> Comments welcome!
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc