Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78637
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <5458D492.9040207@lsces.co.uk>
Date: Tue, 04 Nov 2014 13:28:50 +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 <internals@lists.php.net>
References: <5458CEAF.7060204@lsces.co.uk> <CABRjmp_UJz7BExqFyXdB35-KQ3BANPV0UqKhJz64njFzEKyNvA@mail.gmail.com>
In-Reply-To: <CABRjmp_UJz7BExqFyXdB35-KQ3BANPV0UqKhJz64njFzEKyNvA@mail.gmail.com>
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 13:13, Florian Margaine wrote:
>     On the basis of 'If it's not broken', what is actually broken, and what
>     is just a matter of 'I don't like that way of working'?
> 
>     I have a working Annotation system that has not changed since I started
>     working with PHP. PHPEclise simple displays the information from the
>     docblock comments and allows me to open the relevant file. I can then
>     review the other functions available. I can update the material and have
>     even resorted to porting files and adding extra notes when trying to
>     decipher other peoples work.
> 
>     The problem these days is that projects are stripping the docblock data
>     as 'not the modern way of doing things' and we end up with code that
>     does not work with the IDE. Fortunately DVCS systems have some other
>     advantages and one can cherry pick code changes while maintaining a
>     different style of working.
> 
>     In addition to 'Annotation', there is a lot of discussion about adding
>     types into the code. Having moved to using arrays to pass data to
>     functions, the docblock material includes details on what is required in
>     the hash, something that you will never get from any of the current
>     discussions?
> 
>     Just to add to the fun, PHPEclipse seems to have lost support and while
>     I have learnt enough Java in the past to fix a few little niggles,
>     currently it is unable to cope with a number of new developments in PHP
>     so I'm stuck on just what IS the next move ... While it would be nice to
>     get on with some new code, nothing is stable enough these days to allow
>     that :(
> 
> Right now, I'm afraid your emails looks like a rant more than anything
> else. I'm absolutely certain that you have something interesting to say,
> but the message just didn't get through. Could you elaborate?

Just that what many of us have used for years is coming under increasing
pressure as other people promote their own way of working. In the past
we have been able to co-exist, but it is becoming increasingly difficult
as people 'update' coding styles. Anything that is added to the 'core'
WILL be used to update third party code, but the rest of the
infrastructure is simply not keeping up.

-- 
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