Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80132
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.217.182 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CAF+90c8KjgojwgFYDUwMWYk+gv+ENNSncb_oYVf3WJ+ymdv37w@mail.gmail.com>
References: <CAF+90c8KjgojwgFYDUwMWYk+gv+ENNSncb_oYVf3WJ+ymdv37w@mail.gmail.com>
Date: Sat, 3 Jan 2015 16:57:15 -0800
Message-ID: <CAESVnVqQLe-UeiPitHukoOvGedhBXEOKQgPOWUKG4qjZbKhtdQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: 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: pollita@php.net (Sara Golemon)

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.