Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70457 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79268 invoked from network); 30 Nov 2013 12:37:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Nov 2013 12:37:44 -0000 Authentication-Results: pb1.pair.com header.from=ellison.terry@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ellison.terry@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender) X-PHP-List-Original-Sender: ellison.terry@gmail.com X-Host-Fingerprint: 74.125.82.45 mail-wg0-f45.google.com Received: from [74.125.82.45] ([74.125.82.45:48762] helo=mail-wg0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1F/B1-03478-71CD9925 for ; Sat, 30 Nov 2013 07:37:44 -0500 Received: by mail-wg0-f45.google.com with SMTP id y10so8480180wgg.12 for ; Sat, 30 Nov 2013 04:37:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=RmHcjIiMrviDZed1KbKQzsi0GWcUJjn8XWO0cMP6DvQ=; b=YFBFH70YzJKB8DjYW3UsnAUshPTPaVwJa13HD2zGLfMoVJlP2SCTj+GtkbDl0WAcF8 5rcfdVbdWCmH9KFL+2BflJDnL5UwpQUjXGiwVvIov6hFzmn2xixPzklTafDeKRKEvwjo xQAn8AeFBSIxSuH9x3fQnjEf4qxnW3rxzFexzS+KrZEOBWVwgZzKKHuni7X9pcZfF2MM z8rzq0Z+4fwOXu/8xWfb8SIHKLlEDL83H9qf3mOGTZvtWgGwrq0GMEIl1z+YioKsRhu4 2kiMK8zlPBx740e598BaaPaiOby88GcHzfdwJEI1cy0yQsqjaohbaN4eWjjTgVFSyMN2 Dn+Q== X-Received: by 10.180.74.45 with SMTP id q13mr10470395wiv.47.1385815061093; Sat, 30 Nov 2013 04:37:41 -0800 (PST) Received: from [192.168.1.91] (host81-152-194-204.range81-152.btcentralplus.com. [81.152.194.204]) by mx.google.com with ESMTPSA id o9sm32466858wib.10.2013.11.30.04.37.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 30 Nov 2013 04:37:40 -0800 (PST) Message-ID: <5299DC12.8010100@gmail.com> Date: Sat, 30 Nov 2013 12:37:38 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Nikita Popov CC: PHP Internals References: <4E.7B.51208.63ACD825@pb1.pair.com> <528E1AF6.9050201@php.net> In-Reply-To: Content-Type: multipart/alternative; boundary="------------060403080502040902040502" Subject: Re: [PHP-DEV] RFC: phpdbg From: ellison.terry@gmail.com (Terry Ellison) --------------060403080502040902040502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 30/11/13 10:41, Nikita Popov wrote: > Independently from phpdbg, is there any particular (technical) reason that > prevents (zend?) extensions from registering SAPIs? Could we add something > for that to work? Nikita, if you think about it the SAPI contains main() -- or the respective shared library master entry point, and acts as the calling / callback framework for the Zend environment. To make the SAPI an extension would require inverting this PHP Zend architecture so that there is some sort of general minimal wrapper which can then layer in an additional personality by loading in some shared library from some context. However, this wouldn't be a Zend or PHP extension as we know it. This would involve a lot of work. Thinking off the top of my head, what we could possibly do would be to hook some of the standard entries in the CLI SAPI so that a SAPI-aware extension could insert itself into this chain and modify the behaviour of the standard CLI (or potentially other) SAPIs. This approach could allow phpdbg to be a Zend Extension "skin" on the standard CLI. Regards Terry --------------060403080502040902040502--