Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74006
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.128.175 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAEZPtU61V63QAqMdhLU-U-jf-GP+8F371unFP6DWUY5DWbd23Q@mail.gmail.com>
References: <CAEZPtU61V63QAqMdhLU-U-jf-GP+8F371unFP6DWUY5DWbd23Q@mail.gmail.com>
Date: Wed, 7 May 2014 14:33:21 +0400
Message-ID: <CA+9eiLub-dmkg7CJRP4pX1u4PiZdc=RNDHUee9u9sFbzzYcUDQ@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b2e0707bedc9f04f8cce4a9
Subject: Re: [PHP-DEV] [phpng] naming
From: dmitry@zend.com (Dmitry Stogov)

--047d7b2e0707bedc9f04f8cce4a9
Content-Type: text/plain; charset=UTF-8

I would be just glad. Having clear uniform naming would be fine.
We should just come to agreement about the actual names and I don't think
it's a big problem.

Thanks. Dmitry.


On Wed, May 7, 2014 at 12:54 PM, Pierre Joye <pierre.php@gmail.com> wrote:

> hi,
>
> would it be possible to "clean up" the naming while being at it?
>
> I would prefer longer but clearer/less confusing names rather than
> trying to reduce the type strokes.
>
> For example:
>
> ZVAL_ARR() > ZVAL_ARRAY
> ZVAL_NEW_ARR()  > ZVAL_NEW_ARRAY (btw, ZVAL_NEW_ARRAY is wrongly
> documented in the wiki draft, section about arrays)
>
> Other engine's APIs use full names, to go back and forth between these
> convention is error prone and not too clean. Thoughts?
>
> Yes, it is a detail, but better to fix this now than latter :)
>
> Cheers,
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--047d7b2e0707bedc9f04f8cce4a9--