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

Bug #16302 Exception class is detected as 4.0.0 code
Submitted: 2009-06-07 22:09 UTC
From: till Assigned: mekras
Status: Closed Package: PHP_CompatInfo (version 1.9.0)
PHP Version: 5.2.9 OS: n/a
Roadmaps: 1.9.1    
Subscription  


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 : 38 - 34 = ?

 
 [2009-06-07 22:09 UTC] till (Till Klampaeckel)
Description: ------------ In regard to our email, here is the bug and my initial email: Hey Laurent, been messing with PHP_CompatInfo for a small project, I noticed the following code is said to be PHP 4.0.0: Test script: --------------- shell# echo "<?php Foo_Exception extends Exception {}" >> ./test-pci.php shell# pci -f test-pci.php +-----------------------------+---------+---+------------+--------------------+ | File | Version | C | Extensions | Constants/Tokens | +-----------------------------+---------+---+------------+--------------------+ | test-pci.php | 4.0.0 | 0 | | | +-----------------------------+---------+---+------------+--------------------+ Expected result: ---------------- 5.0.0 Actual result: -------------- 4.0.0

Comments

 [2010-11-19 00:12 UTC] mekras (Mikhail Krasilnikov)
 [2010-11-19 00:15 UTC] mekras (Mikhail Krasilnikov)
This is because PHP_CompatInfo doesn't process "extends" statements. Attached patch fixes this.
 [2010-11-19 00:56 UTC] mekras (Mikhail Krasilnikov)
 [2010-11-19 00:56 UTC] mekras (Mikhail Krasilnikov)
And a test case for this bug.
 [2010-12-06 14:22 UTC] mekras (Mikhail Krasilnikov)
-Status: Open +Status: Assigned -Assigned To: +Assigned To: mekras -Roadmap Versions: 1.10.0a1 +Roadmap Versions: 1.9.1
 [2010-12-08 13:18 UTC] mekras (Mikhail Krasilnikov)
-Status: Assigned +Status: Closed
This bug has been fixed in SVN. 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. Fixed in SVN revision 306073.