Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78644 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54876 invoked from network); 4 Nov 2014 16:07:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Nov 2014 16:07:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:47644] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FA/28-06676-ED9F8545 for ; Tue, 04 Nov 2014 11:07:58 -0500 Received: (qmail 30369 invoked by uid 89); 4 Nov 2014 16:07:55 -0000 Received: by simscan 1.3.1 ppid: 30360, pid: 30366, t: 0.2000s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.163.79.60) by mail4.serversure.net with ESMTPA; 4 Nov 2014 16:07:55 -0000 Message-ID: <5458F9DA.7060308@lsces.co.uk> Date: Tue, 04 Nov 2014 16:07:54 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: PHP internals References: <5458CEAF.7060204@lsces.co.uk> <5458D492.9040207@lsces.co.uk> <5458E306.50006@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Debugging code ... From: lester@lsces.co.uk (Lester Caine) On 04/11/14 14:51, Kristopher wrote: > Every IDE I've used has always working nicely with docblock annotation > and typing and has provided the facilities people seem to think should > be built in to PHP. > > You understand you don't have to use these new features, right? You can > continue using comment-driven DocBlocks and not use any typing. They are > purely optional features. That argument falls flat on it's face when primary libraries upgrade to use 'the new standards' at the expense of compatibility with previous practices. Keeping compatible versions running just complicates matters when the target infrastructure is changing daily :( > To advocate not adding the features simply because you don't want them, > when they are plenty of other people who do want them and do find a use > for them, is pretty selfish. Have I said ANYTHING about not fixing bug such as perhaps making PHP work with Unicode properly? > It's also pretty arrogant to assume your workflow and setup will work > for everyone, and that they should just deal with it. All I am saying is that many of the complaints being made by others that PHP is missing 'important facilities' has a counter that in many cases there is no problem if you use a different method of working. Some of us do perhaps need to document better the alternative way of doing things, and I DO think that loading down the core engine with facilities which are better provided by secondary tools is the wrong approach. However since PHP has a modular structure, it should also be possible to leave out components that are not essential to actually run the code? It is perhaps just making a case for what is needed to improve the functionality of the engine, and what - like the debuggers - can be kept as non-essential secondary tools? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk