I'm not sure what the precedent is for creating a separate list fork for a specific topic. Can one of you who knows the answer to that respond to Richard's suggestion?
As for an RFC, I completely agree. However, it's still a bit too vague to create an RFC that would be of any value. We at least have to brainstorm conceptually where we want to go before an RFC could serve any purpose IMHO. --Kris 2012/2/27 Johannes Schlüter <johan...@schlueters.de> > On Mon, 2012-02-27 at 21:05 +0100, Gustavo Lopes wrote: > > On Mon, 27 Feb 2012 20:09:08 +0100, Johannes Schlüter > > <johan...@schlueters.de> wrote: > > > > > On Mon, 2012-02-27 at 13:05 -0600, Richard Lynch wrote: > > >> > > >> I'd have to come up with some OTHER scenario not involving fatal > > >> error, such as: > > >> > > >> strict $db = new DB(); > > > > > > The example is wrong. The new operator will always return an instance > of > > > the given class (or there will be an exception). > > > [...] > > > > > > This is not true. The new operator can return NULL. In fact, the intl > > extension uses this extensively: > > ok, internal stuff can do everything it wants. But it shouldn't. Doing > that is really bad and I wasn't aware of that case. :-) > > And since it's bad another example should be used :-) > > johannes > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
