Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55969
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADG7izUrayGSRANxakAQPvwGW08Q9QbneY8=VntCAK4qB2oE8g@mail.gmail.com>
References: <CADG7izUrayGSRANxakAQPvwGW08Q9QbneY8=VntCAK4qB2oE8g@mail.gmail.com>
Date: Thu, 27 Oct 2011 01:17:19 +0200
Message-ID: <CAEZPtU5Y2PYbqWhcqUjJwWyZ3odM6HzHC33j-7JkmEUBPrAaHQ@mail.gmail.com>
To: mario@include-once.org
Cc: "Matthew Weier O'Phinney" <weierophinney@php.net>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] SplClassLoader and PSR-0 break language semantics
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Oct 27, 2011 at 1:07 AM,  <mario@include-once.org> wrote:
> 2011/10/26 Matthew Weier O'Phinney <weierophinney@php.net>:
>>
>> My main point, however, is that the standard was ratified quite some
>> time ago already -- we just now have parties interested in creating a
>> C-level implementation compatible with the standard to (a) make usage
>> simpler, and (b) better optimize performance. We should not be debating
>> the standard here, just the implementation.
>>
>
> I'd like to object there. Now that we are discussing it on an open mailing
> list again, both seem actually quite relevant.

Well, my personal opinion here is that you should discuss that in an
open list somewhere and put the RFC together, with examples, docs and
updated patch. The internals list is not really well suited to discuss
that, while I won't mind to have such discussions here, it may make
more sense to have a dedicated list. As it won't be the last
discussion you will have :)

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org