Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74236
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_02B60CD2-5573-485D-AA8E-692797343BE5"
Message-ID: <AEE5BE34-FF47-46B1-92FC-96F51526C062@ajf.me>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Date: Thu, 15 May 2014 20:12:41 +0100
References: <52699BBD.5030407@ajf.me>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <52699BBD.5030407@ajf.me>
Subject: Re: [PHP-DEV] [RFC] list() Reference Assignment
From: ajf@ajf.me (Andrea Faulds)

--Apple-Mail=_02B60CD2-5573-485D-AA8E-692797343BE5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Good evening,

So, I came back to this today. It appears to me that it=92s actually =
impossible for me to implement this feature properly at the present =
moment, due to the parser directly emitting opcodes. This is a shame. =
Unfortunately, there=92s really nothing I can do about it.

Hence, I hereby withdraw my RFC.

Thanks.

On 24 Oct 2013, at 23:14, Andrea Faulds <ajf@ajf.me> wrote:

> Good evening again,
>=20
> Previously I wrote to this mailing list about my proposal to add =
reference assignment to list() with a new syntax ("[PHP-DEV] Proposal: =
Implement FR #7930 (list() constructor reference assignment)"). I have =
now opened an RFC:
>=20
> https://wiki.php.net/rfc/list_reference_assignment
>=20
> In brief, this allows you to write this:
>=20
> $array =3D [1, 2];
> $a =3D $array[0];
> $b =3D &$array[1];
>=20
> Like this instead:
>=20
> $array =3D [1, 2];
> list($a, &$b) =3D $array;
>=20
> Reference assignments with list() work just like normal assignments, =
and you can still skip variables, use nested list()s, and use list() in =
foreach as usual.
>=20
> There is a patch with a passing test, however a memory leak bug was =
found (thanks Nikita!), and so the patch can't be considered complete or =
final yet. I'm something of a novice at debugging PHP code at the =
moment, so any help fixing that would be appreciated, but I will try to =
fix it when I have more time.
>=20
> The patch is here: https://bugs.php.net/bug.php?id=3D6768
>=20
> The RFC has been added to the list in Under Discussion.
>=20
> Any thoughts, suggestions, etc. appreciated.
>=20
> Regards,
> --=20
> Andrea Faulds
> http://ajf.me/
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20

--
Andrea Faulds
http://ajf.me/





--Apple-Mail=_02B60CD2-5573-485D-AA8E-692797343BE5--