how old is this version of PHP?

[Tamara Temple]

Looking into a problem for someone who is using Godaddy Shared Web Hosting (I know..), I noticed the version tag reported by phpinfo is:


PHP API 20041225
PHP Extension 20060613
Zend Extension 220060519

Just how old is this version of PHP??

[Camilo Sperberg]

Post by Tamara Temple
PHP API 20041225
PHP Extension 20060613
Zend Extension 220060519
Just how old is this version of PHP??
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

According to my google search, it should be 5.2.9, so it isn't "that" old:


http://devzone.zend.com/1442/compiling-php-extensions-with-zend-server/

CD onto the extension's source dir (in our example, the PHP version is 5.2.9 as it is the current stable version Zend Server is shipped with):

$ cd /usr/local/zend/share/php-source/php-5.2.9/ext/pspell
Run phpize:

$ /usr/local/zend/bin/phpize
Output should be similar to this:

/Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519/


Greetings.


Met vriendelijke groet,
Camilo Sperberg

----------------
W: http://unreal4u.com
T: http://twitter.com/unreal4u

[Tamara Temple]

Post by Camilo Sperberg

Post by Tamara Temple
PHP API 20041225
PHP Extension 20060613
Zend Extension 220060519
Just how old is this version of PHP??
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

http://devzone.zend.com/1442/compiling-php-extensions-with-zend-server/
$ cd /usr/local/zend/share/php-source/php-5.2.9/ext/pspell
$ /usr/local/zend/bin/phpize
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519/

That would be neat if there was any shell access.

[Larry Garfield]

Post by Tamara Temple
PHP API 20041225
PHP Extension 20060613
Zend Extension 220060519
Just how old is this version of PHP??
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

5.2.9 was released in February of 2009. 5.2 is completely retired and
out of support. 5.3 is on security-only life-support. 5.4 is the
legacy stable release.

Yes, 5.2.9 IS that old. :-) Really, get a host that has made it into
this decade. (GoDaddy apparently doesn't meet that qualification.)
You're doing clients a disservice by allowing them to run such an
ancient and unsupported version.

--Larry Garfield

[Thomas Punt]

Godaddy enables you to upgrade to PHP 5.3 in the cPanel settings.

Date: Mon, 19 Aug 2013 01:07:17 -0500
Subject: Re: [PHP] how old is this version of PHP?
5.2.9 was released in February of 2009. 5.2 is completely retired and
out of support. 5.3 is on security-only life-support. 5.4 is the
legacy stable release.
Yes, 5.2.9 IS that old. :-) Really, get a host that has made it into
this decade. (GoDaddy apparently doesn't meet that qualification.)
You're doing clients a disservice by allowing them to run such an
ancient and unsupported version.
--Larry Garfield
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[Lester Caine]

5.2.9 was released in February of 2009. 5.2 is completely retired and out of
support. 5.3 is on security-only life-support. 5.4 is the legacy stable release.
Yes, 5.2.9 IS that old. :-) Really, get a host that has made it into this
decade. (GoDaddy apparently doesn't meet that qualification.) You're doing
clients a disservice by allowing them to run such an ancient and unsupported
version.

While the statements are correct, many users are not in a position to move from
their currently working systems to even 5.3 let alone 5.4. There is still a lot
of legacy code that unless a few more people step up and help bring it forward
for the many - non programming - users who are stuck with legacy applications,
they will remain requiring 5.2 to run. ISPs got caught out when they arbitrarily
moved accounts forward, and GoDaddy have even been caught by that, so
maintaining a LTS version of PHP5.2 is the lesser evil ... Windows 2000 is
supposed to be dead, but *I* still have sites reliant on it because the code and
hardware is unsupported in even XP. Saying something is dead only works if there
is an affordable way of moving forward ;)
--
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

[Jeff Burcher]

I apologize if this is off topic, but this raises a question for me. Why
can't new versions be backwards compatible? Is it really that difficult to
accomplish? This has been a complaint of mine for years with Windows ever
since we went from 95 to 98. I am an AS400 programmer and I have legacy
programs written in RPG II, which died 20 years ago, and they still run fine
on the newest version of AS400 or iSeries or Power System or whatever the
heck it is called now. I also have PHP scripts that are many years old that
work just fine the way they are, if a new version doesn't come along and
make me have to reprogram for no reason just because it can't handle older
code. Really, have Do loops and data calls changed that much over the years?
I mean, all you do is set a condition, use a variable key field, and voila,
data is pulled and processed, no big deal. Yeah, you can get fancy with it,
but the core basics are still the same. I have been programming for over 35
years and like to think that once a program is built it should run forever.
Do we just accept that we have to rewrite every program we ever wrote every
time a new version comes out? A little extreme, but you get my point.
Comments? Suggestions?

(I am also the kind of guy who thinks quality made hand tools from the 1800s
are superior to many purchased today at Lowes or Home Depot.)

Thanks,

Jeff Burcher - IT Dept
Allred Metal Stamping Works
"Making Metal Parts since 1946."

-----Original Message-----
Sent: Monday, August 19, 2013 6:24 AM
Subject: Re: [PHP] how old is this version of PHP?

Post by Larry Garfield
5.2.9 was released in February of 2009. 5.2 is completely retired and
out of support. 5.3 is on security-only life-support. 5.4 is the

legacy stable

release.

Post by Larry Garfield
Yes, 5.2.9 IS that old. :-) Really, get a host that has made it into
this decade. (GoDaddy apparently doesn't meet that qualification.)
You're doing clients a disservice by allowing them to run such an
ancient and unsupported version.

While the statements are correct, many users are not in a position to move
from their currently working systems to even 5.3 let alone 5.4. There is

still a

lot of legacy code that unless a few more people step up and help bring it
forward for the many - non programming - users who are stuck with legacy
applications, they will remain requiring 5.2 to run. ISPs got caught out

when

they arbitrarily moved accounts forward, and GoDaddy have even been
caught by that, so maintaining a LTS version of PHP5.2 is the lesser evil

...

Windows 2000 is supposed to be dead, but *I* still have sites reliant on

it

because the code and hardware is unsupported in even XP. Saying
something is dead only works if there is an affordable way of moving

forward

;)
--
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
--
http://www.php.net/unsub.php

[Sebastian Krebs]

Post by Jeff Burcher
I apologize if this is off topic, but this raises a question for me. Why
can't new versions be backwards compatible? Is it really that difficult to
accomplish? This has been a complaint of mine for years with Windows ever
since we went from 95 to 98. I am an AS400 programmer and I have legacy
programs written in RPG II, which died 20 years ago, and they still run fine
on the newest version of AS400 or iSeries or Power System or whatever the
heck it is called now. I also have PHP scripts that are many years old that
work just fine the way they are, if a new version doesn't come along and
make me have to reprogram for no reason just because it can't handle older
code. Really, have Do loops and data calls changed that much over the years?
I mean, all you do is set a condition, use a variable key field, and voila,
data is pulled and processed, no big deal. Yeah, you can get fancy with it,
but the core basics are still the same. I have been programming for over 35
years and like to think that once a program is built it should run forever.
Do we just accept that we have to rewrite every program we ever wrote every
time a new version comes out? A little extreme, but you get my point.
Comments? Suggestions?

My 2 cent: I hadn't any major issues with BC since 5.3 and from 5.2 it
required a little bit to do, but was solveable (means: It wasn't
complicated, but only an afternoon time to invest). Caine complaints from
time to time his codebase here. That is nothing new and I am unsure how
representative his statements are.

Regards,
Sebastian

Post by Jeff Burcher
(I am also the kind of guy who thinks quality made hand tools from the 1800s
are superior to many purchased today at Lowes or Home Depot.)
Thanks,
Jeff Burcher - IT Dept
Allred Metal Stamping Works
"Making Metal Parts since 1946."

-----Original Message-----
Sent: Monday, August 19, 2013 6:24 AM
Subject: Re: [PHP] how old is this version of PHP?

Post by Larry Garfield
5.2.9 was released in February of 2009. 5.2 is completely retired and
out of support. 5.3 is on security-only life-support. 5.4 is the

legacy stable

release.

Post by Larry Garfield
Yes, 5.2.9 IS that old. :-) Really, get a host that has made it into
this decade. (GoDaddy apparently doesn't meet that qualification.)
You're doing clients a disservice by allowing them to run such an
ancient and unsupported version.

While the statements are correct, many users are not in a position to

move

from their currently working systems to even 5.3 let alone 5.4. There is

still a

lot of legacy code that unless a few more people step up and help bring

it

forward for the many - non programming - users who are stuck with legacy
applications, they will remain requiring 5.2 to run. ISPs got caught out

when

they arbitrarily moved accounts forward, and GoDaddy have even been
caught by that, so maintaining a LTS version of PHP5.2 is the lesser evil

...

Windows 2000 is supposed to be dead, but *I* still have sites reliant on

it

because the code and hardware is unsupported in even XP. Saying
something is dead only works if there is an affordable way of moving

forward

;)
--
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

--
http://www.php.net/unsub.php

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[Lester Caine]

Post by Sebastian Krebs

Post by Jeff Burcher
Do we just accept that we have to rewrite every program we ever wrote every

Post by Jeff Burcher
time a new version comes out? A little extreme, but you get my point.
Comments? Suggestions?

My 2 cent: I hadn't any major issues with BC since 5.3 and from 5.2 it
required a little bit to do, but was solveable (means: It wasn't
complicated, but only an afternoon time to invest). Caine complaints from
time to time his codebase here. That is nothing new and I am unsure how
representative his statements are.

My 'problem' came about through taking over a couple of small hosting companies
who had sites across several ISP's and various versions of PHP ( and ASP thrown
in for good measure ). Every site required a day or so's work to tidy up, and
little problems thrown in like the <?= cock-up which took down 5 sites when that
ISP 'upgraded' PHP to the problem version. But the main problem still is making
things E_STRICT compliant since PHP5.4 tends to be set up with it enabled and
PHP5.3 will be fazed out on ISP's at some point.

I'm slowly moving sites to servers where I do have control of the framework, but
'just an afternoons work' across a large number of sites and fire fighting when
sites go down without prior warning all takes time ... I can't really complain,
I've been picking up customers who's sites have been affected and earning money
from them :) I have to say no to a lot though as there are only so many hours in
a day.
--
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

[Larry Garfield]

Far too much is made of BC breaks between PHP versions. Well-behaved
code should still be working a decade later.

The catch is that "well behaved" gets tighter each release. For example:

$foo = "hello";
$bar = "world";
print $foo[$bar];

In PHP 5.3 and earlier, $bar is a string which makes no sense as an
index of a string. It needs to be an int. PHP therefore casts that to
an int, gets 0, and you get "h".

In PHP 5.4, that was acknowledged as a bug (which it always was), and
now triggers a Warning. Because, really, it always was a bug but just
failed silently before. Now it tells you so you can fix it. It looks
like a BC break, though, because "I get an error I didn't used to".

Other things are, eg, removing register_globals and magic_quotes, which
have been deprecated for about 12 years and if you were still using them
now then your code should break. :-) They're a security hole. But
those are very few and far between.

--Larry Garfield

Post by Jeff Burcher
I apologize if this is off topic, but this raises a question for me. Why
can't new versions be backwards compatible? Is it really that difficult to
accomplish? This has been a complaint of mine for years with Windows ever
since we went from 95 to 98. I am an AS400 programmer and I have legacy
programs written in RPG II, which died 20 years ago, and they still run fine
on the newest version of AS400 or iSeries or Power System or whatever the
heck it is called now. I also have PHP scripts that are many years old that
work just fine the way they are, if a new version doesn't come along and
make me have to reprogram for no reason just because it can't handle older
code. Really, have Do loops and data calls changed that much over the years?
I mean, all you do is set a condition, use a variable key field, and voila,
data is pulled and processed, no big deal. Yeah, you can get fancy with it,
but the core basics are still the same. I have been programming for over 35
years and like to think that once a program is built it should run forever.
Do we just accept that we have to rewrite every program we ever wrote every
time a new version comes out? A little extreme, but you get my point.
Comments? Suggestions?
(I am also the kind of guy who thinks quality made hand tools from the 1800s
are superior to many purchased today at Lowes or Home Depot.)
Thanks,
Jeff Burcher - IT Dept
Allred Metal Stamping Works
"Making Metal Parts since 1946."

-----Original Message-----
Sent: Monday, August 19, 2013 6:24 AM
Subject: Re: [PHP] how old is this version of PHP?

Post by Larry Garfield
5.2.9 was released in February of 2009. 5.2 is completely retired and
out of support. 5.3 is on security-only life-support. 5.4 is the

legacy stable

release.

Post by Larry Garfield
Yes, 5.2.9 IS that old. :-) Really, get a host that has made it into
this decade. (GoDaddy apparently doesn't meet that qualification.)
You're doing clients a disservice by allowing them to run such an
ancient and unsupported version.

While the statements are correct, many users are not in a position to move
from their currently working systems to even 5.3 let alone 5.4. There is

still a

lot of legacy code that unless a few more people step up and help bring it
forward for the many - non programming - users who are stuck with legacy
applications, they will remain requiring 5.2 to run. ISPs got caught out

when

they arbitrarily moved accounts forward, and GoDaddy have even been
caught by that, so maintaining a LTS version of PHP5.2 is the lesser evil

...

Windows 2000 is supposed to be dead, but *I* still have sites reliant on

it

because the code and hardware is unsupported in even XP. Saying
something is dead only works if there is an affordable way of moving

forward

;)
--
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
--
http://www.php.net/unsub.php