Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67607
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5466EBBB-C74D-4498-9DBD-338F460694A5@schlueters.de>
References: <CAAyV7nG126YkpOF-EShHbf=4rgX7gQ2VE0ShRh0-50_Yr--h4g@mail.gmail.com>
	<CAEZPtU5HPu7O8SC5qHjxaz86Zms=SaXoRE3EXmCfmU8z2aT62A@mail.gmail.com>
	<5466EBBB-C74D-4498-9DBD-338F460694A5@schlueters.de>
Date: Sun, 2 Jun 2013 13:07:43 +0200
Message-ID: <CAEZPtU7BhXMjGd+ooAB+fnNS3=QEbugV=M8x1haxcS_aKhE+Xg@mail.gmail.com>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] 5.NEXT Integer and String type modifications
From: pierre.php@gmail.com (Pierre Joye)

On Sun, Jun 2, 2013 at 11:11 AM, Johannes Schl=FCter
<johannes@schlueters.de> wrote:
>
>
> On Jun 2, 2013, at 8:34, Pierre Joye <pierre.php@gmail.com> wrote:
>
>>> Obviously there's a pretty significant ABI break here. I propose a "twe=
ak"
>>> of the Z_* macros to "fix" that. Basically, Z_STRLEN() will cast the re=
sult
>>> to an int. This is the same behavior as today, and will mean that exist=
ing
>>> extensions continue to function exactly as today. But new extensions (a=
nd
>>> elsewhere in core) can use a new macro Z_STRSIZE() which will return th=
e
>>> native size_t.
>>
>> A new macro will be a good solution, but I would name it what it
>> actually is, Z_SIZE_T.
>
> That's not what it is. It is the length of the string aka. var.value.str.=
length as such it should indicate its relation to a string. So something li=
ke Z_STRSIZE is  correct (and the name is nice thinking about Unicode strin=
gs where length (characters) !=3D size (bytes))

It is size_t. There is no such thing as unicode or multibyte string
length in php but in mbstring, intl or iconv, to name a few. php
strings are buffers, and buffers lengths use size_t.

This macro (and other) are about extension developers, working in  C,
not about what its representation in userland. Even if they are
closely related, obviously.

The day we will have actual multi bytes/unicode strings, we will need
a separate length to represent in characters (be multi bytes).

Cheers,
--
Pierre

@pierrejoye | http://www.libgd.org