Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80146 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87371 invoked from network); 4 Jan 2015 13:02:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2015 13:02:52 -0000 Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.212.180 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.212.180 mail-wi0-f180.google.com Received: from [209.85.212.180] ([209.85.212.180:43812] helo=mail-wi0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 45/11-15455-BF939A45 for ; Sun, 04 Jan 2015 08:02:51 -0500 Received: by mail-wi0-f180.google.com with SMTP id n3so1752873wiv.7 for ; Sun, 04 Jan 2015 05:02:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=N9aSheM4EWoE6sWR803YFRkqIZ6WaqYJ05DBgDJlpwE=; b=CmCSHKCUrPjLemxA5fpQqzIu3B8CTFwPaqE5d9Fp6IDk8xrebJUiGw9npysQFYwrPl 8a/pBQIr742PXSy47Ls2Qxx4nGtasGblJowtiWA+71eycIgOOotHbWUxYIc9osnKwCxx quIWnRWqLvS+WD2B1+psWhf2viaZVHhO8NdFe9nEi0pe1GxIsWHlEBbsXkMc3Gm72+ls SfI3LWGE8+6yzFv0D8JgUbHC3FwehKlUU2mGgEA3XpfgZ3hXNrIhJQ+/G+GlbLzhGcJc EAYW4dFLzDjmqLKZrLVIr6UTvH4iHTX8QMub99JnT+SjVavar2ViqeuG1yuyXnflc6hW 30Mg== X-Gm-Message-State: ALoCoQleKpjwXMVHq0Ez6Y54SWNDbSs6dURBLZQF8Abrtb28ZRoXEcmoZ7WL+20KLDRKG8Z0z86O MIME-Version: 1.0 X-Received: by 10.180.218.39 with SMTP id pd7mr15809019wic.21.1420376568582; Sun, 04 Jan 2015 05:02:48 -0800 (PST) Received: by 10.194.57.73 with HTTP; Sun, 4 Jan 2015 05:02:48 -0800 (PST) X-Originating-IP: [77.11.123.69] In-Reply-To: References: Date: Sun, 4 Jan 2015 14:02:48 +0100 Message-ID: To: reeze Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a1134cd58d16d91050bd330a2 Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files From: kontakt@beberlei.de (Benjamin Eberlei) --001a1134cd58d16d91050bd330a2 Content-Type: text/plain; charset=UTF-8 Hey reeze, This looks like a fantastic approach. Can you explain how you compile the PHP code into the Shared Object? The README doesnt explain much. greetings Benjamin On Sun, Jan 4, 2015 at 1:33 PM, reeze wrote: > I like the idea, I have implemented a util [1] to help writing extensions > with PHP, I try the approach HHVM adopted by embedding PHP scripts to the > binary file of extension, maybe it is what you want. I do like it been > supported in core. I would like to implement the RFC if others like it. > > --- > [1] https://github.com/reeze/php-ext-embed > > > On 4 January 2015 at 19:52, Benjamin Eberlei wrote: > >> Hey everyone, >> >> I want to open discussion on my RFC to strengthen the ability of >> extensions >> to provide functionality to developers in both C **and** PHP code. >> >> For this extensions can add PHP files to a list of "prepend files" that >> are >> part of every request execution exactly the same way the INI >> auto_prepend_file functionality works: >> >> https://wiki.php.net/rfc/extension_prepend_files >> >> I propose implementation details in the RFC, but they are completely up to >> discussion. I am even sure there is probably a better way than what I >> proposed, because I am not familiar with the code. >> >> greetings >> Benjamin >> > > --001a1134cd58d16d91050bd330a2--