Re: Debugging code ...
| From: | Florian Margaine | Date: | Tue, 04 Nov 2014 14:01:17 +0000 |
| Subject: | Re: Debugging code ... | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78638@lists.php.net to get a copy of this message | ||
Hi,
On Tue, Nov 4, 2014 at 2:28 PM, Lester Caine <lester@lsces.co.uk> wrote:
> 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.
>
I'm sorry... I may be stupid. I'm not sure I understand what you want to
say.
I have a guess though: are you saying that, for example, PHPEclipse at its
version from 2008 can't cope up with PHP at its version from 2014?
>
> --
> 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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Regards,
--
Florian Margaine