Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82090
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <037301d042c4$e58eab20$b0ac0160$@tekwire.net>
References: <54D3EE95.2080109@lerdorf.com>
	<CAFp73Xsc52fMfaZXGLq5fShJdnv3nxk=74O4N7si=pmxBP1EQw@mail.gmail.com>
	<E0D67F55-95C3-49E0-A94C-7B0E2E66B952@lerdorf.com>
	<CAEZPtU64LGNs3box_0E+c8jQ3oE1oRHnbYbD8_eGA+Se6KigXg@mail.gmail.com>
	<035f01d04281$e1133090$a33991b0$@tekwire.net>
	<CAEZPtU5RU8_3DaROiuKB5n0jv7qRd6wq65OM9O0cUQNKSAZRiA@mail.gmail.com>
	<037301d042c4$e58eab20$b0ac0160$@tekwire.net>
Date: Sat, 7 Feb 2015 18:05:49 +0700
Message-ID: <CAEZPtU5yNp4oysu-WjzhB534mvubcZB6KP=RfJ_0bu7+LH0EJA@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>
Cc: Rasmus Lerdorf <rasmus@lerdorf.com>, Guilherme Blanco <guilhermeblanco@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3c7b41267ab050e7d8524
Subject: RE: [PHP-DEV] Annotated PHP 5->7 extension diff
From: pierre.php@gmail.com (Pierre Joye)

--001a11c3c7b41267ab050e7d8524
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Feb 7, 2015 5:57 PM, "Fran=C3=A7ois Laupretre" <francois@tekwire.net> wr=
ote:
>
> > De : Pierre Joye [mailto:pierre.php@gmail.com]
> > Not sure it will help. It is really about showing cases for deref,
> > duplicate, convert, iterate, etc. The zpp, return values or
> > functions/class/methods declaration are really the easy part here.
>
> I understand. I thought it would be a nice way to enhance the abstraction
layer php-ext-gen provides, as I am missing use cases. Generating glue code
is just one of the project objectives. The second one is to provide an
abstraction layer allowing to duplicate as few code as possible when
migrating an extension to PHP 7 (HHVM is also in scope).
>
> I already fully abstract resources, so that user code doesn't have to
deal, for instance, with zend_resource structs. I also provide an API for
persistent resources, which Zend does not provide. That's just an example.
It can be done for many other areas.
>
> But, if you don't want to participate, I'll integrate that myself using
your examples.

It is more a time issue and a non believer in too much generation of codes.

> Just a question : for your demo extension, would you write two branches
or a single one with #ifdef directives ?

I ported one (not oss sadly) and I end up with separate files. One for 5.x,
7.x and common helpers.

> Cheers
>
> Fran=C3=A7ois
>
>

--001a11c3c7b41267ab050e7d8524--