> On Friday, August 8, 2003, at 09:21 AM, Dan Phiffer wrote:
> > I'm working on an ongoing project that depends on a shared webserver
> > running
> > an old version of PHP (4.1.2 I believe). Is there any good reason to
> > stick
> > with an older version of PHP, or might it be a valid suggestion to
> > have it
> > upgraded to something a bit more recent? I have a notion that upgrade
> > attempts may have been snubbed out by the way things like
> > register_globals
> > are now handled by default, the perception being that newer versions
> > of PHP
> > are incompatible with older code.
> the register globals "event" happened on 4.1 (from memory), so any
> install over that should be straight forward. in any case, it's just
> one simple directive that needs to be changed in the php.ini file...
> can't see how this should be an issue.
> i think the best reason to keep up-to-date on the versions is that each
> new release is "better, more stable, etc etc"... i haven't ever heard
> anyone on this list say "i prefer 4.2.3 over 4.2.4" :)
> as a programmer, i hate it how some hosts refuse to keep on top of the
> upgrades... really useful functions in newer versions aren't available.
> > Mainly I'm concerned that code I test on our in-house server running
> > version-current PHP will depend on function calls and language
> > constructs
> > that the production server's vintage PHP interpreter lacks.
> exactly... there isn't a HUGE number of differences between the current
> release and what they've got on the live server, but there are
> exceptions... i was making good use of file_get_contents() on my LAN,
> but had to write a user-function to te it when running on the
> live server which is stuck at 4.2.3 for the moment.
> it's almost a case of "don't upgrade your LAN until the production
> server upgrades", but I prefer "convince you host to upgrade, or move
> host" :)
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php