| Justin Patrin 2005-06-08, 8:57 pm |
| On 6/8/05, Joe Stump <joe@joestump.net> wrote:
> It's a bad idea in your opinion, but in my opinion as the sole
> programmer who maintains 50,000 lines of PHP4 OOP code (and, yes, all
> but a few lines is OOP) not to mention the thousands of lines of PEAR
> code I use, this would be great.
I also maintain a sizeable chunk of PHP4 OOP code and have not started
even trying to port it precisely because it's such a daunting task.
>=20
> I'd just love to see a patch. My site gets about 12 million visits a
> month and about 40 million raw requests month so the idea of
> migrating my code to PHP5 is quite daunting. I can't simply "upgrade"
> because there's, literally, thousands of lines of code that haven't
> been touched in years.
Yes it needs to be tested, but PHP4 code will work perfectly well in
PHP5. Just turn off E_STRICT mode and "var" works just fine. I still
don't see why you would need PHP5 syntax in PHP4. Sure you wouldn't be
using "private" and "protected" but those are really just syntax sugar
anyway. Upgrade your dev to PHP5, check for errors, fix code, then
actually upgrade to PHP5 and start trying to deal with the "new"
object model. (Actually IMHO there really isn't all that much
different, but I digress...)
>=20
> It's not a great idea for a wide release, possibly, but I'd probably
> PAY someone to make this patch so I could start "porting" my PHP4
> code to PHP5 before making a final push to make sure it all works
> fine in PHP5.
>=20
> At least this way all of my code would be PHP5 "ready" and then I
> could upgrade my dev and staging servers before moving all my code
> onto the live site. I could also continue to push code that looks
> like PHP5 into the live site.
It's already PHP5 ready.
>=20
> Just sayin' - it would make *my* transition easier.
>=20
> --Joe
>=20
>=20
> On Jun 8, 2005, at 2:16 PM, Justin Patrin wrote:
>=20
>=20
>=20
--=20
Justin Patrin
|