Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70264 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48914 invoked from network); 21 Nov 2013 15:15:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2013 15:15:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.217.169 mail-lb0-f169.google.com Received: from [209.85.217.169] ([209.85.217.169:57689] helo=mail-lb0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B4/52-36839-4832E825 for ; Thu, 21 Nov 2013 10:15:17 -0500 Received: by mail-lb0-f169.google.com with SMTP id y6so3151235lbh.14 for ; Thu, 21 Nov 2013 07:15:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ClnfCyt+EejqCm8hyhmSciGDISga6oJzNjbyr4NaaCc=; b=sc3B5Z9FT5LMbi2sOCNR/eRqzCd8L0lzLX1+f/UIjwBLxDW1m6GfQx8GfEWK6k/qJG BcT9kCO7wvdfKL7E6NVpfSfhTGl2nufzdPpB+hhnAT7VUmcUtX11MVxfuBHYAKmr0CXU t0Tq3vN2rGWG/0TWpSZUq/Br+T7TYXNeRjzwRNDgYe+KgOSh9D/T0m9ZLYvBdZAxbOyk vQHJHq49VNAwPv7xqXicgZ3u6oTz7WpaD9kJgNuUHRi+OEvgc9NIcXIjT1Nfs/ZyFCTr AYZVMYiL4n265yOG6w/Onq33K5E/VRpafgnhLk6/HZPOeUhbRF9nmyGAKfGlVAvY4Lkl HaXA== MIME-Version: 1.0 X-Received: by 10.152.28.37 with SMTP id y5mr5345238lag.23.1385046913909; Thu, 21 Nov 2013 07:15:13 -0800 (PST) Sender: mike.php.net@gmail.com Received: by 10.114.184.19 with HTTP; Thu, 21 Nov 2013 07:15:13 -0800 (PST) In-Reply-To: <528E1EA3.9090906@php.net> References: <4E.7B.51208.63ACD825@pb1.pair.com> <528E1AF6.9050201@php.net> <528E1EA3.9090906@php.net> Date: Thu, 21 Nov 2013 16:15:13 +0100 X-Google-Sender-Auth: KaC-TbCGVmLqG20CQbQF8FWL6U4 Message-ID: To: Joe Watkins Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] RFC: phpdbg From: mike@php.net (Michael Wallner) On 21 November 2013 15:54, Joe Watkins wrote: > On 11/21/2013 02:43 PM, Michael Wallner wrote: >> >> On 21 November 2013 15:38, Joe Watkins wrote: >>> >>> On 11/21/2013 02:20 PM, Nikita Popov wrote: >> >> >>>> I'm probably missing some context here, maybe you could explain how >>>> phpdbg >>>> differs from something like xdebug? I mean, xdebug seems to be the >>>> de-facto >>>> debugging extension for PHP and has been for a long time, but we're not >>>> bundling it. Why should we bundle phpdbg instead? >>> >>> >>> This is not an extension, it is a SAPI module. The build system >>> does >>> not support external SAPI modules, the implementation requires Zend API >>> which is not exported (or wasn't, has since been patched). >> >> >> That still does not answer the question, though?! >> >> > > Yes, it does. > > xdebug has a reasonable route to deployment already, it, and none of it's > users, benefit at all from xdebug being bundled. > > This is not the same, it can be deployed outside of the source tree but it's > much harder, for most people, and for some impossible. > > I was happy writing code, getting a few functions exported and deploying to > those people with the ability to build ... > > I don't much care for anything but writing the code, and will go back to > that now ... Sorry, I actually only meant the first question: what's the difference to xdebug? I don't care yet about bundling, I don't event know what it is. -- Regards, Mike