Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80173
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.45 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CAESVnVqQLe-UeiPitHukoOvGedhBXEOKQgPOWUKG4qjZbKhtdQ@mail.gmail.com>
References: <CAF+90c8KjgojwgFYDUwMWYk+gv+ENNSncb_oYVf3WJ+ymdv37w@mail.gmail.com>
	<CAESVnVqQLe-UeiPitHukoOvGedhBXEOKQgPOWUKG4qjZbKhtdQ@mail.gmail.com>
Date: Mon, 5 Jan 2015 07:18:25 -0700
Message-ID: <CAFMT4NrVFzGF3YroZrMdXBmde74MVWMziDfHVmJasLG3wDCNog@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PHP 7 API naming conventions: str vs string
From: levim@php.net (Levi Morrison)

On Sat, Jan 3, 2015 at 5:57 PM, Sara Golemon <pollita@php.net> wrote:
> On Sat, Jan 3, 2015 at 3:42 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:
>> Or maybe be more explicit and use "cstr" for C strings. (For symmetry the
>> zend_string type could become zstr.)
>>
> I personally prefer cstr/zstr for explicitness, but agree that the
> main focus should be consistency.
>
> -Sara
>
> And yes, the fact that smart_string deals with char* while smart_str
> deals with zstring, but smart_str used to be the char* API.  That's a
> big bucket of clown.

I favor 'zstr' and 'cstr' over something like 'str' and 'string'.
Perhaps zend_zstr_ would seem a bit redundant (zend zend string) but
better than ambiguity and having to look it up.