Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43579
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.44.30 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=xGEBuoNeqR++T+beL6HG3ossAf56/crWmQ2B+N7JpIjnN1I31ZQiEcofj+rZK0vzA8
         MN0ljijjHHId7gx7gYUUBcD+ftf4DQ7ypxkKZFZYUwnINjOamRZSMk6YDXlVmWucohaM
         47T7R92Sl8dr25qO6sCHNURdFtmmLlnh05IYs=
MIME-Version: 1.0
In-Reply-To: <1238595978.5733.9.camel@goldfinger>
References: <af54caaf0903301606s26d87824oedd1167db8f0cc10@mail.gmail.com> 
	<29CF2C07F9044405AF6332BE2F3A373F@PC3EE1F19287> <af54caaf0904010624p3b1f1b26h4f925c731436afc3@mail.gmail.com> 
	<1238595978.5733.9.camel@goldfinger>
Date: Wed, 1 Apr 2009 16:16:20 +0100
Message-ID: <af54caaf0904010816i52bad7f9te23293a12d9488d3@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Nuno Lopes <nlopess@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: Removing the Zend API
From: paul.biggar@gmail.com (Paul Biggar)

2009/4/1 Johannes Schl=C3=BCter <johannes@schlueters.de>:
> Hi,
>
> On Wed, 2009-04-01 at 14:24 +0100, Paul Biggar wrote:
>> > Moreover, in your example in the wiki you don't include how you would =
do
>> > parameter parsing. Or do you rely on the code generator to look at the=
 C
>> > functions signatures and figure out by itself what to do? (actually th=
ere is
>> > some ambiguity, AFAIR, and thus guessing cannot be done reliably)
>>
>> That is exactly right. (I'll make this clearer in the RFC). I can't
>> think of any cases where guess cannot be done reliably. If you can
>> give me an example, I'll try and address it.
>
> Well, take your example:
>
> void Y(char *, int)
>
> Is the second parameter the length of the string or something
> independent? Is the char* changed? And who is going to free it?

Good points. I had initially thought that there should be some simple
declarative DSL, and later thought 'why can't it be a header file in
the simple case'. I guess this is why.

I think that to handle more complex cases we need the kind of
information which makes it straightforward to easily generate code to
make a seamless interface between C and the engine API. The only case
I had thought of was to somehow mangle structs/pointers into
resources. But I suppose we need lengths for strings. I expect (many?)
more of these cases will come up.


(Of course, this is why I recommended a SoC project to try it)


Thanks for the comments, I'll update the RFC.
Paul



--=20
Paul Biggar
paul.biggar@gmail.com