Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71414
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.46 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <alpine.DEB.2.10.1401221933540.6067@whisky.home.derickrethans.nl>
References: <CAESVnVq3=+_N-c5e1n==c=w9Og82FM24pBqJJt66yS-Swru0TA@mail.gmail.com>
 <2D2D996C-9455-4DD1-9669-90AFAF591E32@strojny.net> <CAGa2bXZ_8non-C8bpoPXvVFCgmPcEZ-RAm3U6wFJ+FGgw8aW=w@mail.gmail.com>
 <alpine.DEB.2.10.1401221933540.6067@whisky.home.derickrethans.nl>
Date: Thu, 23 Jan 2014 06:22:49 +0900
Message-ID: <CAGa2bXbs=J3AM7vifGrDCZYXji-bNvbnkNqCzjQXPJGkvAajNg@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Lars Strojny <lars@strojny.net>, Sara Golemon <pollita@php.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b33da5c74b66e04f095bc77
Subject: Re: [PHP-DEV] [RFC] __debug_info()
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--047d7b33da5c74b66e04f095bc77
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Derick,

On Thu, Jan 23, 2014 at 3:35 AM, Derick Rethans <derick@php.net> wrote:

> > Hi all,
> >
> > Sorry for off topic.
> >
> > On Wed, Jan 22, 2014 at 6:37 AM, Lars Strojny <lars@strojny.net> wrote:
> >
> > > Love it, two things: the var_dump() properties will be replaced (not
> > > merged) with the "real" properties in the object (I am asking as that
> would
> > > make it very very cool for stuff like doctrine, where lazy loaded
> entities
> > > are way too large to dump)? As for the name, I would prefer
> __debugInfo()
> > > as in __callStatic(). I know there is __set_state() but that's
> something
> > > that needs deprecation and fixing :)
> >
> >
> > Could anyone add __setState() for 5.6?
>
> Why would you want to do that? If at all, all the *newer* methods should
> be __debug_info etc. __set_state was first and changing it to
> __setState() would mean that var_export'ed() variables in < PHP 5.6
> would now no longer work? Or the other way around? It's a cosmetic
> change that helps nobody=E2=80=94just like renaming other standard functi=
ons to
> make them more "organised".
>
> cheers,


I mean add alias for __set_state() to keep consistent names.
__set_state() should be there very long time or forever for compatibility.

It's small cosmetic change, but it would assure PHP to be a good
language to learn in the future. IMHO.

Anyway, I would like to write RFC for aliasing. Aliases may be added
in the future.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--047d7b33da5c74b66e04f095bc77--