Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53405
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain openmv.com from 64.15.152.204 cause and error)
To: "'Robert Eisele'" <robert@xarg.org>
Cc: <internals@lists.php.net>
References: <BANLkTi=qbj_=dmNv__RN4LkDY4GgbTtGYQ@mail.gmail.com> <BANLkTikipDXeO-wj0gch__6PErqcbGZfmA@mail.gmail.com>
In-Reply-To: <BANLkTikipDXeO-wj0gch__6PErqcbGZfmA@mail.gmail.com>
Date: Mon, 20 Jun 2011 10:18:43 -0400
Message-ID: <007c01cc2f54$f6a15bb0$e3e41310$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AcwvS7hr8zoVrh5eTwmuuAcbgOnvzAAA+Vxg
Content-Language: en-ca
Subject: RE: [PHP-DEV] foreach() for strings
From: jbondc@openmv.com ("Jonathan Bond-Caron")

On Mon Jun 20 09:11 AM, Lee davis wrote:
>=20
> Could we also use current(), next() and key() for iteration of =
strings?
>=20
> $string =3D 'string';
> while ($char =3D current($string))
> {
> echo key($string)   // Would output the offset position I assume 0,1,2
> etc??
> echo $char          // outputs each letter of string
> next($string);
> }
>=20

Hopefully it can be supported without sacrificing too much performance
Like others mentioned, it seems important to distinguish between =
binary/byte
and text iteration.

$string =3D new ByteIterator('string =E9');
foreach($string as $i =3D> $byte)=20
  ...

$string =3D new TextIterator('string =E9');
foreach($string as $i =3D> $char)=20
  ...

When most developers get a 'string' from a database, my hunch is they =
assume
they would be iterating over the 'characters' (utf8, iso.. encoding) and =
not
individual bytes.

So +1 to string iteration as long as there's byte iteration and some =
plan
for text iteration / by character (with icu or not).