Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61460
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
Content-Type: multipart/signed; boundary="Apple-Mail=_76CB9D42-4036-4FA5-AA1E-7F08B78A75A1"; protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Thu, 19 Jul 2012 12:05:35 +0400
Message-ID: <64223D01-8F4C-4B65-AD6C-5C425EC0EA68@gmail.com>
To: internals internals <internals@lists.php.net>
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Regarding PHP6, string/array APIs
From: indeyets@gmail.com (Alexey Zakhlestin)

--Apple-Mail=_76CB9D42-4036-4FA5-AA1E-7F08B78A75A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Stas made a good point about need to start with new API, which then can =
be followed by syntactic sugar.

So, we need some ideas to start with:

1. A lot of people told, that it would be a good idea to come with a =
written standard regarding arguments order. I don't care what it will =
be, as long as it will be documented.

2. It would be really useful to have 2 versions of each function: one =
which mutates the variable and one which returns the new variable.

Example:

    <?php
      $src =3D 'SoUrCe';
      $result =3D lowered($src); // $result =3D=3D 'source', $src =3D=3D =
'SoUrCe'
      $result =3D lower($srd);   // $result =3D=3D true,     $src =3D =
'source'
    ?>

3. Speaking of implementation=85 Functions, which return slice of =
string/array could be made to reference the same memory-areas as the =
source strings/arrays. That is until the first modification, of course. =
Kinda advanced copy-on-write semantics. I know something like that is =
implemented in D http://dlang.org/d-array-article.html and Go

4. casting between strings and arrays of characters would be a great =
thing to have too. this way, useful array-oriented functions could be =
applied to strings=

--Apple-Mail=_76CB9D42-4036-4FA5-AA1E-7F08B78A75A1
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)

iQEcBAEBAgAGBQJQB7/QAAoJEM8kLGy4PJ4JJxMIAJSgcfLL8LT9Gz7Uvl0/7Cgz
hr9sVgBUgXuw7WQ5cHPH6Umf6sN6MBOkLyWVr9ZGGrYJAGPVcJJBB9KhQ7ZReZFT
/bfQLZdQWuJLzUjPXu8VzD9WWYhCBgGxd0fM4f6VZ9uAm7utKR1rO93LHWFHrw8p
6dHheYxnZu5l67ofN9TvFND68yGT4YeyhYJJZORZO/wnjyYWtA8nUUgBke74jciQ
NwH92wZl+G6dajdVHQ+Xk9fZf0PxecFAIBkMVGccRjBEvzst/I8gsP9G7s+oXHxQ
Eu7c8jPX/5n4AZBh+Y3RAL4jXpRyPNm3VQ+S9oNk4QSRd+w9ATw0fQOUDAVa3fY=
=MKpF
-----END PGP SIGNATURE-----

--Apple-Mail=_76CB9D42-4036-4FA5-AA1E-7F08B78A75A1--