Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61865
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.220.170 cause and error)
MIME-Version: 1.0
Date: Sat, 28 Jul 2012 18:13:10 -0400
Message-ID: <CADqTB_iyyaPZgRCdiB_YL+c53FR0EzDV+uYfR-SEcz24Z-i9dQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: notes on a couple of RFCs
From: rasmus@mindplay.dk (Rasmus Schultz)

Is this RFC outdated?

https://wiki.php.net/rfc/jsonable

We have JsonSerializable in 5.4 - this appears to be essentially the same thing?

(Should it be moved from "draft" to "implemented", or should it just
be removed? It was not implemented with the names used in this RFC.)

I was also looking at the following RFC:

https://wiki.php.net/rfc/linecontrol

I have often wondered about something similar - although I don't like
what's proposed here as far as syntax. We already have syntax for
directives - building on that, I would expect to see something like
this:

    declare(file='source.tpl#3');

This would affect error-reporting of all lines following that line.
Using the directive block-syntax, this would affect error-reporting
only within the block:

    declare(file='source.tpl#3') { ... }

I've been hungry for this feature for many years - it would pave the
way for huge improvements in template-engines, AOP frameworks,
pre-processors, code-generators, and meta-programming in general...
most php-developers shy away from most of these powerful patterns,
because there is currently no way to implement "proper"
error-reporting for any of these patterns...