On Thu, 12 Jul 2007 07:13:07 +0100, Lester Caine <[EMAIL PROTECTED]> wrote:
> Tijnema wrote:
>> Yes, that's what I meant to say, they can be implemented on top of,
>> just like the above mentioned json, it is implemented on top of too.
>> But, that means that a regular PHP programmer doesn't need PHP5 for
>> his scripts (except for OO if they want). Do you think it matters to
>> them if their scripts run on PHP4 or PHP5?
>
> THIS is the basic problem. There is no reason that - with a certain amount
> of
> tidying up - current PHP4 code could not just be run on PHP5. If you don't
> like OO you don't need to use it and nothing in PHP5 REQUIRES that it is
> used.
>
>> And so, most will stuck on, "If it isn't broken, don't fix it". Since
>> PHP4 isn't really broken, a lot people won't "fix it".
>
> I think that is what is currently being said. As from now on you use PHP4
> at
> your own risk and nothing more will be fixed. Personally I STARTED with
> PHP5
> even before it was released as I had simply ASSUMED that PHP4 would be
> phased
> out long before now, but I am getting more and more bogged down with
> people
> complaining that my PHP5 stuff will not work on PHP4. Up until now I have
> tried to oblige, but we need this definitive statement and a proper
> movement
> forward otherwise we will have to support stuff across PHP4,5 and 6.
>
> Having SAID that - the problems with things being broken between different
> VERSIONS of PHP5.x are the REAL reason that PHP5 take up has not been so
> good.
> I STILL haven't got some of my code to RUN on PHP5.2 - although I suspect
> that
> the main reason is the fact that it DOES still run in PHP4! ( And PHP5.1
> ). So
> this is another reason for wanting to be able to say - all new development
> is
> PHP5.2 only use version xxx for PHP4 but no further work will be done on
> that
> branch, and end of lifeing PHP4 would at least encourage that.
Something just occurred to me that might satisfy both sides of the issue.
What about the way Apache handles their versions of Apache (1.x and 2.x).
That is to say; they haven't abandoned 1.3 (no surprise, as I think it still
has the biggest install base). They simply maintain security related issues.
ppl still continue to build modules for 1.3. ppl still continue to run/install
it.
Apache doesn't hide it in some back corner. Everybody's happy. Would this
approach not be an acceptable "EOL" for PHP4?
Just a thought.
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
> L.S.Caine Electronic Services - http://home.lsces.co.uk
> MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
> Firebird - http://www.firebirdsql.org/index.php
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
/////////////////////////////////////////////////////
Service provided by hitOmeter.NET internet messaging!
.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
