Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78641
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5458E306.50006@lsces.co.uk>
References: <5458CEAF.7060204@lsces.co.uk> <CABRjmp_UJz7BExqFyXdB35-KQ3BANPV0UqKhJz64njFzEKyNvA@mail.gmail.com>
 <5458D492.9040207@lsces.co.uk> <CABRjmp_EGV+esSi7u9jRL0n+h1O63f4FLr5_0c_yT0FETZKq-w@mail.gmail.com>
 <5458E306.50006@lsces.co.uk>
Date: Tue, 4 Nov 2014 15:45:44 +0100
Message-ID: <CAEU6NAfzm44jNE2UYH_AJRBF6=hxne+VXuO2zBkKqGDzeaE7tw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013d0f8ad6d2b30507098587
Subject: Re: [PHP-DEV] Debugging code ...
From: peter.e.lind@gmail.com (Peter Lind)

--089e013d0f8ad6d2b30507098587
Content-Type: text/plain; charset=UTF-8

It sounds like you're suggesting that all work on PHP that does not boil
down to bug fixes be stopped.

I'd suggest an alternative: fork PHP and only merge bugfixes in to your own
version. Best of both worlds, you get to keep your beloved PHP pristine
without any of the cumbersome new features, and the rest of us can enjoy an
evolving language.

On 4 November 2014 15:30, Lester Caine <lester@lsces.co.uk> wrote:

> On 04/11/14 14:01, Florian Margaine wrote:
> > Hi,
> >
> > On Tue, Nov 4, 2014 at 2:28 PM, Lester Caine <lester@lsces.co.uk
> > <mailto: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?
>
> 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. The problem with keeping the available IDE's up to
> date with the current code is secondary and PHPEclipse just happens to
> be my preference, but if I switch to other options I find similar lag in
> support for key features. Learning a new platform is a bigger stopper
> currently than living with the holes and I will probably fix the problem
> with :: before giving up in and changing ... but it would be nice not to
> have the hassle.
>
> --
> 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
>
>


-- 
<hype>
WWW: plphp.dk / plind.dk
CV: careers.stackoverflow.com/peterlind
LinkedIn: plind
Twitter: kafe15
</hype>

--089e013d0f8ad6d2b30507098587--