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

Bug #16372 phpdt confused by "{$var}" notation
Submitted: 2009-06-24 12:05 UTC
From: digger Assigned: izi
Status: Closed Package: Testing_DocTest (version 0.4.0)
PHP Version: 5.2.9 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 : 31 - 7 = ?

 
 [2009-06-24 12:05 UTC] digger (Dave Walton)
Description: ------------ When the "{$var}" notation is used in a class method, phpdt loses track of the fact that it is in a class, and reports the following methods as functions. Test script: --------------- <?php /** * <code> * $test = new MyClass(); * // expects: * </code> */ class MyClass { /** * <code> * $test = new MyClass(); * // expects: * </code> */ public function __construct() { $x = "asdf"; $y = "{$x}"; } /** * <code> * $test = new MyClass(); * // expects: * </code> */ public function test() { } } ?> Expected result: ---------------- $ phpdt test.php Processing test.php [PASS] class MyClass [PASS] method MyClass::__construct [PASS] method MyClass::test Total time : 0.1011 sec. Passed tests : 3 Skipped tests : 0 Failed tests : 0 Actual result: -------------- $ phpdt test.php Processing test.php [PASS] class MyClass [PASS] method MyClass::__construct [PASS] function test Total time : 0.1011 sec. Passed tests : 3 Skipped tests : 0 Failed tests : 0

Comments

 [2009-06-25 15:19 UTC] izi (David Jean Louis)
-Status: Open +Status: Closed -Assigned To: +Assigned To: izi
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.