Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61373
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.42 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_C37EE575-919E-4F83-B029-51B963F249CD"; protocol="application/pgp-signature"; micalg=pgp-sha1
In-Reply-To: <5005A5E4.2030004@sugarcrm.com>
Date: Tue, 17 Jul 2012 22:47:13 +0400
Cc: Pierre Joye <pierre.php@gmail.com>,
 Gustavo Lopes <glopes@nebm.ist.utl.pt>,
 internals <internals@lists.php.net>,
 Andrew Faulds <ajfweb@googlemail.com>
Message-ID: <B2840BE0-3E89-4B34-A96F-9A3DF412FE93@gmail.com>
References: <CAN+gjSe7r2SoRNYufcaB2ktK05shH1AcAsaFSbUibF9r4TeRrw@mail.gmail.com> <op.whkdiodaidpuyk@damnation> <CAEZPtU5Rb9W8iydy2-hoYqGDSWqd9WCTUXh214O-uCc3nVNiVA@mail.gmail.com> <50059AF8.5050805@sugarcrm.com> <9430CE0C-7DA4-4655-92D5-056E12A7BC74@gmail.com> <5005A5E4.2030004@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] Pseudo-objects (methods on arrays, strings, etc.)
From: indeyets@gmail.com (Alexey Zakhlestin)

--Apple-Mail=_C37EE575-919E-4F83-B029-51B963F249CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 17.07.2012, at 21:50, Stas Malyshev wrote:

> Hi!
>=20
>> I am for making array a proper class with methods.
>>=20
>> "Legacy" functions can be implemented as wrappers around it:
>>=20
>>    function array_push(&$array, $value)
>>    {
>>        $array->push($value);
>>    }
>=20
> The problem there is that array has different semantics than object. =
Not
> completely, but for example if you pass array to function, it is =
passed
> by value and is not modified, but objects are always mutable when =
passed
> to functions. Changing this semantics will break a lot of code.

Having special handling of Array objects doesn't sound good too. And I =
don't see any nice solution.

Options are:
* "5-to-6" tool, similar to python's "2-to-3" converter, which will fix =
code.
* introduce some kind of per-file declare() option, which would enable =
pass-by-reference semantics of arrays/strings/etc. in 5.5 which would =
let people write the same code for 5.5 and 6.x

Well, actually, there's one more option: we can introduce "Autocloned" =
interface (empty, without methods) and force "cloning" of objects, which =
implement this interface, during parameter-fetching phase.
This would allow us to have 2 sets of classes: One set which implements =
this interface (slower, but backwards-compatible) and another set which =
doesn't (faster, but not compatible).=

--Apple-Mail=_C37EE575-919E-4F83-B029-51B963F249CD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQEcBAEBAgAGBQJQBbMyAAoJEM8kLGy4PJ4JlAcIAJ/YYFYiLoYqlTLjR1+svvNS
4bk/VlsdcguCyPvvDddcfiyIdwrz9+G1YCgXBMjJVRZXsIM5yQgbsuncEwnj7x/h
SuHfT9+9WNgseRAIfNz8iOFG9MrmI5SiSwEipus/Yg+VAbq4JyFYLElvJqPZomvs
chonSfeb5PcuIBujjBT8vJvh8qJGuRoy896KsM+zn17yoqAocnIYjOrRPIH7sQ/6
wAn9M8IiuJeFrR+3ag/og8muAOdCIFMewErn2L+VESCSutza1FzNab9AdKyyJc6K
LHe2JuJNl1q3dxXGlMyZ2nOJW3uSBGwcAcgoaDxocE1ECD2L4qRQP/dvKDx4TlA=
=sj57
-----END PGP SIGNATURE-----

--Apple-Mail=_C37EE575-919E-4F83-B029-51B963F249CD--