Perhaps rather than killing it we should just emphasize it more in the 
documentation (ie on preg_replace and not only in pattern modifiers). 

But I have found the /e modifier to be very useful in the past. Unfortunately, 
just having woken up I can't remember exactly where and how I used it, lol. 

Perhaps another option, if it's a security concern is the ability to turn off 
the /e modifier, and have it off by default. This way we can protect our less 
experienced programmers, while keeping it available for more advanced use 
cases. 

Just my two cents + inflation

- Mike

Sent from my iPhone

On Feb 5, 2012, at 10:37 AM, Tom Boutell <t...@punkave.com> wrote:

> A sense of humor is important when reading mailing lists frequented by
> extremely clever people (:
> 
> On Sun, Feb 5, 2012 at 11:34 AM, Reindl Harald <h.rei...@thelounge.net> wrote:
>> 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....@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!
>> 
> 
> 
> 
> -- 
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com
> window.punkave.com
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
> 

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to