Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80367 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76571 invoked from network); 11 Jan 2015 13:39:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2015 13:39:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:27454] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/70-06196-41D72B45 for ; Sun, 11 Jan 2015 08:39:33 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 1FD614B0226; Sun, 11 Jan 2015 14:37:22 +0100 (CET) Reply-To: To: "'Pierre Joye'" , "'Sara Golemon'" Cc: "'Stanislav Malyshev'" , "'PHP internals'" References: <54B1AA31.6050703@gmail.com> In-Reply-To: Date: Sun, 11 Jan 2015 14:39:24 +0100 Message-ID: <002301d02da4$034d7a00$09e86e00$@tekwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHdpO6kBDBjSAQ05ND+I0bfKmNeFQIeJCUTAflXB0ABzhWVu5xw0C1Q Content-Language: fr X-Antivirus: avast! (VPS 150111-0, 11/01/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] One API to rule them all? (Was: Extension Prepend Files) From: francois@tekwire.net (=?UTF-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Pierre Joye [mailto:pierre.php@gmail.com] > > More than adding a new layer, I would love to see something similar to > hhvm or Zephir available by default. If C is used, then only the > relevant parts have to be implement by the developers, skipping all > the over complicated data mangling, swapping, exchange, etc between > userland and the engine. It is then relatively easy to end up > generating codes for either php, hhvm or any other platform. Using > builtin script (yes, in this case it could be a nice thing), it could > became a very nice way to develop php&co extensions. > > For what I can imagine (I did not remotely try to implement it yet) is > to find a way to parse, say, a php script which include custom > sections for C (or C++) codes. We could use comments but I do not like > the idea, mainly because it will be tricky to have editors support :) I am not sure we need a real language here (PHP or other). I would first = wait to see if a set of C macros can't do the job. Cheers Fran=C3=A7ois