Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80130
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <CAF+90c8KjgojwgFYDUwMWYk+gv+ENNSncb_oYVf3WJ+ymdv37w@mail.gmail.com>
Date: Sat, 3 Jan 2015 23:46:15 +0000
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <BD7AF36B-CFB4-400D-ABEA-7DDB51FD93F3@ajf.me>
References: <CAF+90c8KjgojwgFYDUwMWYk+gv+ENNSncb_oYVf3WJ+ymdv37w@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] PHP 7 API naming conventions: str vs string
From: ajf@ajf.me (Andrea Faulds)

Hey Nikita,

> On 3 Jan 2015, at 23:42, Nikita Popov <nikita.ppv@gmail.com> wrote:
>=20
> Basically if you have two APIs, one using str, the other using string, =
you
> can't tell which one is for C strings and which one is for =
zend_strings. It
> could be either way.
>=20
> It would be nice to have a convention for this and stick with it. E.g.
> "string" is for zend_strings and "str" for C strings.
>=20
> Or maybe be more explicit and use "cstr" for C strings. (For symmetry =
the
> zend_string type could become zstr.)

The abbreviation seems rather pointless, I=E2=80=99d rather string over =
str.

I=E2=80=99d suggest this convention:

* Use =E2=80=9Cstring=E2=80=9D or omit the suffix for zend_string
* Use =E2=80=9Ccstring=E2=80=9D for C strings (char*)
* Don=E2=80=99t use =E2=80=9Cstr=E2=80=9D

That sound good?
--
Andrea Faulds
http://ajf.me/