Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78321 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6687 invoked from network); 25 Oct 2014 06:14:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Oct 2014 06:14:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.212.180 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.212.180 mail-wi0-f180.google.com Received: from [209.85.212.180] ([209.85.212.180:55402] helo=mail-wi0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 24/71-28285-AAF3B445 for ; Sat, 25 Oct 2014 02:14:02 -0400 Received: by mail-wi0-f180.google.com with SMTP id em10so2762108wid.1 for ; Fri, 24 Oct 2014 23:13:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; bh=MBCeERSCuso1c9BrcD4kibS+vSbBod8hHZhMQxOkuYw=; b=l45zneGOJVi/owXZ6Ob5eoOf/XWanHOv21RT7+6yo8qNbfOEsHAY0ofzQ4cXZ8tltI pRCOMSqTUrbo8U6mZ3GaWpITS4i9V59H3uMqkPktSw6z4OcVtUE93XiEItzt0w2yXgqw arB5+0B66fg7Nm+qRu4GTMRYxMR5q4gDuRLfyjQoZFBpuyEsGV03vKEUyl3mSVWMj3Xd zd4cCM/PgGPhRtSpqZJMG+dNqucCAf9RqhfDMUFZdY2UOkpUv/pc8NWdb+/d/6bstHar L3EoAiA1F8vvjaT97BSAtiT6rPZXlhwieanL3ZYhzfBWDMtsK8wVjNMSYQ7XQtY7VDz7 rWDQ== X-Gm-Message-State: ALoCoQkzmnZaYPxUc9sje/Zgth5uAXDCxSbSP3WGvtP5VpuNgjYR84dItrF4mKfDIMUW1N8K0T6x X-Received: by 10.180.211.226 with SMTP id nf2mr8448739wic.61.1414217639247; Fri, 24 Oct 2014 23:13:59 -0700 (PDT) Received: from [192.168.1.67] (host86-164-152-200.range86-164.btcentralplus.com. [86.164.152.200]) by mx.google.com with ESMTPSA id cw6sm7824250wjb.18.2014.10.24.23.13.58 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 24 Oct 2014 23:13:58 -0700 (PDT) Message-ID: <1414217636.2624.89.camel@localhost.localdomain> To: Derick Rethans Cc: Bob Weinand , PHP Developers Mailing List Date: Sat, 25 Oct 2014 07:13:56 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] PHPDBG nonsense (Was: Re: [PHP-CVS] com php-src: Made phpdbg compatible with new engine: ...) From: pthreads@pthreads.org (Joe Watkins) On Fri, 2014-10-24 at 23:06 -0400, Derick Rethans wrote: > On Fri, 24 Oct 2014, Bob Weinand wrote: > > > Commit: 2bcac53bca8ea82d661f057b6d9ff3c7c84f05a7 > > Author: Bob Weinand Fri, 24 Oct 2014 19:29:50 +0200 > > Parents: 53560ca06b333b71883269091f7d74c0a25e087b c03ac47bafd0ea55055a2f3d4de0bc6bb4d98d8d > > Branches: master > > > > Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=2bcac53bca8ea82d661f057b6d9ff3c7c84f05a7 > > > > Log: > > Made phpdbg compatible with new engine > > > > AM sapi/phpdbg/xml.md > > Although this patch does make it work with PHP 7, it also does do > something absolutely different: it reinvents a wheel by coming up with a > new XML protocol for debugging. > > So far I've been silent on PHPDBG, but seriously, is it really not > possible to cooperate instead of reimplementating something that already > exists? PHPDBG is difficult to use with its odd command line "commands". > And then I haven't even spoken about the pretentious "awesomesauce" on > http://phpdbg.com/ — a domain that's not even under the PHP group's > control. > > cheers, > Derick Derick, A few weeks ago, I was at a conference where you told a room filled with hundreds of developers that phpdbg was no good, because you don't know how to use it. This is a strange sort of silence, and does not invite us to co-operate. When you invented dbgp there were other protocols in existence, not sure why we are expected to reuse a protocol. It so happens that the phpstorm guys working on integration seemed keen on something new. I don't see the problem in that. If the only reason it exists is for projects like phpstorm and they are actually going to put time into trying something new, then why the hell not. I'm not sure why it matters what kind of language we use on phpdbg.com, not sure why you think it should be under the control of the php group either. If you had wanted to co-operate, you could have spoken to me at that conference in person, or to any of us in IRC, on any day. You chose to do what pleased you. We should be allowed to do the same. Joe