Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80316
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.215.43 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CAKxcST83pXKCqK8bYDBTn85oWMuqYYczfgg8LHGo=e5jRfv2Bg@mail.gmail.com>
References: <CAESVnVqfoKg=J7BXWf45DFRkEjP9a=TFiDYauD0ZHa-sKXsvDg@mail.gmail.com>
	<CAKxcST83pXKCqK8bYDBTn85oWMuqYYczfgg8LHGo=e5jRfv2Bg@mail.gmail.com>
Date: Fri, 9 Jan 2015 20:14:46 -0800
Message-ID: <CAESVnVrnvhCgCPr1SYdrYU9w+0RRw2-65kkSnwYLMdd3cyMc4A@mail.gmail.com>
To: Paul Dragoonis <dragoonis@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>, 
	"Pierre (php.net gtalk)" <pierre.php@gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] One API to rule them all? (Was: Extension Prepend Files)
From: pollita@php.net (Sara Golemon)

On Fri, Jan 9, 2015 at 5:48 PM, Paul Dragoonis <dragoonis@gmail.com> wrote:
> Somewhat Pie in the sky but at the same time also achievable with good
> planning and design. I'd support this definitely and this abstraction layer
> would solve constant maintainability of extensions by not having to update
> themselves constantly to support latest versions of PHP due to a lack of
> abstraction.
>
Yep.  Exactly what I'm thinking.

I forsee defining this PHP<->Native Interface (I hereby dub it "PNI")
as part of the php-langspec such that part of being a conforming
implementation includes supporting this API.

-Sara