Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.12.2

Bug #617 Warnings from PhpEclipse
Submitted: 2004-01-24 11:00 UTC
From: pear-01 at oliverklee dot de Assigned: danielc
Status: Closed Package: DB
PHP Version: Irrelevant OS: Linux
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 1 + 48 = ?

 
 [2004-01-24 11:00 UTC] pear-01 at oliverklee dot de
Description: ------------ When opening the DB 1.5.0rc2 package in PhpEclipse, I get the following Warnings and Errors for DB.php: Line 229: Error: ';' expected after expression (Found token: Variable($classname)) This can be fixed by changing the line @include_once("DB/${type}.php"); to if (is_array($options) && isset($options["debug"]) && $options["debug"] >= 2) { // expose php errors with sufficient debug level include_once "DB/${type}.php"; } else { @include_once "DB/${type}.php"; } Line 707: ':' expected after 'case' keyword (Found token: ;) Solution: Change case 'limit_count'; $this->limit_count = $value; break; to case 'limit_count': $this->limit_count = $value; break; At line 611: Too many closing '}'; end-of-file not reached. Solution: Count the braces with a good editor (better than PhpEclipse).

Comments

 [2004-01-24 11:07 UTC] pear-01 at oliverklee dot de
Looks like the fix for the first warning also fixes the third one.
 [2004-01-25 00:03 UTC] danielc
The code in this section was changed in CVS about a week ago. Plus, prior to that, I hadn't come across this bug during my extensive testing. You can update your version of DB from CVS or wait a few days and there will be an official new release.
 [2004-01-25 18:40 UTC] pear-01 at oliverklee dot de
I just had a look at the CVS version. The first issue seems to have been fixed, but the issue with the case statements still exists. Reopening.
 [2004-01-25 19:01 UTC] danielc
You're right. Fixed in CVS. Thanks for your report and your persistence.