Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51264
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 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:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=L7laUSHBf9MZWF1aSugjljZMdT3Abu7PDuhSdfOraRElvDWAiTF5Yp2CXuqBivw6nI
         ed8Rx3reQDVtLr5ZR76OyIelcq+I4aJsORYX0y45fpDkvI56znqAur8V7wv68l4Ikz0Z
         Z/5d77CTtKlqyMe7YOcaI73MbRxgCQw2UBbv0=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=m2DFLojhyXtN0OV1C9zNYCcUnmsDF4_THJ9Ek@mail.gmail.com>
References: <AANLkTin3tG3yqFzKxSqNBe6-3k=K2XSYbQmJJYaJnFiy@mail.gmail.com>
 <1294276068.10675.3.camel@guybrush> <AANLkTikdFbNaR_PT8Lnsy-6rtWjT_6uy0dPyOiBGpfE0@mail.gmail.com>
 <AANLkTim725JWw=wcCC7rLY=eyVJKrfPUk2bnWhr_AeFh@mail.gmail.com>
 <4D283A96.3090908@yahoo.com.au> <AANLkTi=eNQYS5-4Zs6BOtfezdexDsxp5zc=+WZzeceuf@mail.gmail.com>
 <AANLkTi=m2DFLojhyXtN0OV1C9zNYCcUnmsDF4_THJ9Ek@mail.gmail.com>
Date: Thu, 13 Jan 2011 10:29:46 -0800
Message-ID: <AANLkTinJrW1CU3smKRgFyk2K=5daVrKc0BHQD7nhDKOu@mail.gmail.com>
To: Martin Scotta <martinscotta@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: about class names as values
From: chadfulton@gmail.com (Chad Fulton)

Take this with a grain of salt, but:

On Thu, Jan 13, 2011 at 7:22 AM, Martin Scotta <martinscotta@gmail.com> wro=
te:
> Hi all,
>
> I don't know how the internal development process of PHP works.
>
> First at all: was this feature approved?

From my experience, don't consider something "approved" until it's in
SVN, and even then maybe not (e.g. type hinting...), regardless of how
many people say "I think that sounds like a good idea".

>
> if that is a "yes"...
> is this feature going to be scheduled for some release?

See below.

> Is it supposed that I will submit a patch?

Mostly, the burden is on the person requesting a feature to submit a
patch, if for no other reason than that everyone is busy and that, as
the requester, you probably have the most interest in getting the
feature implemented.

Once a patch is out there, you're going to need to convince at least
one core dev to get behind your idea, since they are in the position
of getting it into SVN, and they have the best big picture view of
PHP. The core devs do often seem happy to help improve patches, if
they think they're worthwhile.

Then, perhaps it will get into SVN if a core dev likes it and no core
devs oppose it too much.
Then, perhaps it will be scheduled for a release.

>
> Thanks you all,
> =A0Martin Scotta
>