Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66488
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGnunKSWcsZnHjAvpv6VMVzPt_tk4gMhOBciJbGzZ2nHMe_pwA@mail.gmail.com>
References: <CAGnunKSWcsZnHjAvpv6VMVzPt_tk4gMhOBciJbGzZ2nHMe_pwA@mail.gmail.com>
Date: Wed, 6 Mar 2013 13:08:31 +0000
Message-ID: <CAPwsocFr0+LpkBZL5_=rfU4F7nALYxHTe=Q0Mi84x59P0AvkWg@mail.gmail.com>
To: Max Romanovsky <max.romanovsky@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=089e0102ffea6b6c6904d7414902
Subject: Re: [PHP-DEV] Proposed changes to PHP language
From: leight@gmail.com (Leigh)

--089e0102ffea6b6c6904d7414902
Content-Type: text/plain; charset=ISO-8859-1

On 6 March 2013 12:48, Max Romanovsky <max.romanovsky@gmail.com> wrote:

> Dear PHP Community,
>
> I'd like to propose several changes to PHP core:
>
>    1. Allow re-throwing exceptions without losing original stack trace,
>    like in other technologies:
>    try {/*...*/} catch(Exception $e) { throw; }
>

catch (Exception $e) { throw $e; }

This does what you want? (A quick test my end appears to keep the stack
trace in-tact at least)


>    2. Introduce base class for all PHP classes. E.g. Object. It would help
>    in type hinting and allow to add new common methods without any magic.
>

I like this idea.


>    3. Parse body of PUT request in the same manner as it's done for POST
>    request. I guess it should be stored in $_POST array to maintain
> backward
>    compatibility. Otherwise $_REQUEST handling should be aware of new array
>    with PUT data.
>

I don't really like the idea of putting non-POST data in $_POST

It would still be nice to have a better way of handing PUT though.

--089e0102ffea6b6c6904d7414902--