Re: DB_DataObject question

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'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. 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. 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. Just sayin' - it would make *my* transition easier. --Joe On Jun 8, 2005, at 2:16 PM, Justin Patrin wrote:

On 6/8/05, Joe Stump <joe@joestump.net> wrote:

Simple rant ... Would it be too much to ask for PHP developers to alias public/ private/static/const/etc. to "var" in a PHP4 release? How about ignoring said keywords before "function" too? Too much to ask? I'd think aliasing "private" to "var" in a PHP4 version wouldn't be THAT big of a deal.

This is an interesting idea, but the problem is that there would then be syntax in PHP4 which means absolutely nothing. This simply wouldn't make sense to have. Not only that, PHP5 is already out so this would only really make it so that some PHP5 code could run on PHP4, but who knows if it would work right. This would be a very bad idea, IMHO.

Of course, then you have people reading code running on PHP4 that looks like PHP5 code, but doesn't behave as such, but MAN would that make my life a buttload easier as I migrate about 50,000 lines of code from PHP4 -> PHP5. --Joe On Jun 8, 2005, at 1:48 PM, Justin Patrin wrote:

On 6/8/05, Daniel Testa <dan@sbrha.org> wrote:

Which versions of php is DB_Dataobject compatible with? I have one website that runs with php 5 and everything works great and happy. I migrated most of my core code to another web server running php 4.3.11. Doing this causes my php scripts to die whenever they try and use any of the auto generated class files made by createTables.php. They get parse errors. The error Parse error: parse error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home/crazyl2/include/DataObjects/Chr_characters.php on line 12 Can DB_dataobject run in 4.3.11? All the auto generated files come from the php 5 server so could that have something to do with it?

DB_DO works fine with PHP4. However, if you use the generator in PHP5 the generated files will have PHP5 syntax (public instead of var). If you change all of the "public" var declarations to use PHP4 syntax you should be fine. -- Justin Patrin

--Justin Patrin