Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57762
Return-Path: <patrick.allaert@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 63616 invoked from network); 6 Feb 2012 10:16:45 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Feb 2012 10:16:45 -0000
Authentication-Results: pb1.pair.com header.from=patrick.allaert@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=patrick.allaert@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
X-PHP-List-Original-Sender: patrick.allaert@gmail.com
X-Host-Fingerprint: 74.125.82.170 mail-we0-f170.google.com  
Received: from [74.125.82.170] ([74.125.82.170:50835] helo=mail-we0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 2E/21-57508-A88AF2F4 for <internals@lists.php.net>; Mon, 06 Feb 2012 05:16:43 -0500
Received: by werm1 with SMTP id m1so4847595wer.29
        for <internals@lists.php.net>; Mon, 06 Feb 2012 02:16:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        bh=6p/CYVaCU2WsXJ8EpzPWfjSv4goHVcRIa6DrNb3ZR2k=;
        b=iDwpeej14xdZCk6pdFnWDwZtq+QbZ6u8MFpzf3D46K5mTRxLf906p/btIswL+4OMyb
         Q4bYx5t3nTjxYeU+Qd5cjG2QYPYMdTTBVnwJPg8kutw8A0TLjD16aWTdFBcTQK4C6QV1
         dUFs+39//drntSmBlO6MulB7NQT6vewMJYYVU=
MIME-Version: 1.0
Received: by 10.216.137.4 with SMTP id x4mr6732844wei.15.1328523398595; Mon,
 06 Feb 2012 02:16:38 -0800 (PST)
Sender: patrick.allaert@gmail.com
Received: by 10.223.85.195 with HTTP; Mon, 6 Feb 2012 02:16:38 -0800 (PST)
In-Reply-To: <CAMWw8k_VJ8p5Kxe1awHvL3mRGz2pkp-SAg7gQS+PU_TkAgQ99Q@mail.gmail.com>
References: <CAF+90c9qoyzBf+FpBxMdX0FByy5xB+7x3xi3kNxdvWX=_uz=mg@mail.gmail.com>
	<alpine.DEB.2.02.1202051644220.12865@whisky.home.derickrethans.nl>
	<A633CF2D7C7BED41B41F1E64F25507B8069D29BD20@MAILR001.mail.lan>
	<4F2EE658.2010504@sugarcrm.com>
	<CAORXhGK=adtVyXL5vZZyRLLz5c8J_y6Cz4rkPwfxBFXUcRm65Q@mail.gmail.com>
	<CADajX4DNP0=X4TrEn3SsiHU4dULCssQxMW-A-PrksqfGS-As7g@mail.gmail.com>
	<CAMWw8k_VJ8p5Kxe1awHvL3mRGz2pkp-SAg7gQS+PU_TkAgQ99Q@mail.gmail.com>
Date: Mon, 6 Feb 2012 11:16:38 +0100
X-Google-Sender-Auth: Ikedi1fAc2V0Rv1aNUI65ici5rI
Message-ID: <CACwt+JeJjOasDwf9RiywqDiKS4u0yvAi6iUvgm8MyFVxqdzzLA@mail.gmail.com>
To: Gwynne Raskind <gwynne@darkrainfall.org>
Cc: Adam Harvey <aharvey@php.net>, Tom Boutell <tom@punkave.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Deprecate and remove /e modifier from preg_replace
From: patrickallaert@php.net (Patrick ALLAERT)

+1: It does make sense to me for the same reason as Stas mentioned.