Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45770
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.211.201 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=dhMLa0ll9rchJ3fvKbJo01x/pQcPootsWw3o8IMi2Ahk8mblAw1KdwxseLvedvWuxJ
         EZgVTEZ9sCfWOxGOQ65uINHKpnZGB3hRTkNnUKixt3iAqt1dFppI6XqF1DhnpuRBOu1Y
         SgdCcCkhMEAIpn41mEw78YkOuxVLUUT9PgTew=
MIME-Version: 1.0
In-Reply-To: <20091012173621.GO5179@arvo.suso.org>
References: <20091012154610.GJ5179@arvo.suso.org>
	 <bcb7aa500910120851v5b3ee96ew3c9ac8419eefd972@mail.gmail.com>
	 <20091012160854.GK5179@arvo.suso.org> <4AD356D5.2020605@lerdorf.com>
	 <20091012162227.GL5179@arvo.suso.org>
	 <fe05d1540910120927q2d12cecem19d711897aa13f41@mail.gmail.com>
	 <20091012165734.GN5179@arvo.suso.org>
	 <fe05d1540910121012u33fc12c9k82f50b0c8799dd9c@mail.gmail.com>
	 <20091012173621.GO5179@arvo.suso.org>
Date: Mon, 12 Oct 2009 11:14:02 -0700
Message-ID: <e2e02fe0910121114r6cad74d0hef843abf217b2acd@mail.gmail.com>
To: Mark Krenz <mark@suso.org>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Why is ereg being deprecated?
From: chrisstocktonaz@gmail.com (Chris Stockton)

Hello,

On Mon, Oct 12, 2009 at 10:36 AM, Mark Krenz <mark@suso.org> wrote:
> =A0Whenever I bring up an issue like this with the PHP devs, I feel like
> you guys never experience having to support PHP. Among other things, I
> am the main sysadmin for my web hosting company and have been supporting
> PHP since version 3 there. When 4.0 came out, I had to help people
> change their code accordingly to fix any changes and so on with
> subsequent versions.
> .. snip ...
> =A0So for the project developers to just say screw you, we're dropping
> ereg in 6 and you can't do anything about it without giving a chance for
> that information to make its way downstream is pretty cold and will lead
> to a lot of angry people that maybe you don't have to deal with, but the
> rest of us that run servers and maintain code have to deal with.

Just because you did not find the information does not mean it was
unavailable. Assuming developers are saying "screw you" is just
ignorant. No one says you have to upgrade to PHP6 the moment it is
available. you could run PHP5 another 10 years if you choose. If you
choose to go through whatever measures you find necessary then no one
is at fault except for you. Many web hosting companies waited until
after PHP4 was entirely deprecated to upgrade to PHP5, and some,
likely still run PHP4 on some servers for customers to stubborn to
upgrade.

Your assumption of responsibility I find incorrect, your general
approach to this discussion I find distasteful. If it bothers you this
much put a patch out, that can be discussed and perhaps applied
depending on the consensus.

-Chris