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

Bug #10656 no userConfirm() check in Frontend::setFrontendObject
Submitted: 2007-04-08 21:33 UTC
From: tias Assigned: tias
Status: Closed Package: PEAR (version 1.5.1)
PHP Version: Irrelevant OS:
Roadmaps: 1.5.3    

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:
Solve the problem : 36 - 11 = ?

 [2007-04-08 21:33 UTC] tias (Tias Guns)
Description: ------------ Hello, in PEAR_Frontend::setFrontendObject() there is a silly line that sais 'quick test to see if this class implements a few of the most important frontend methods' 1) Decent OO inheritance makes such a check useless 2) It checks for a deprecated method that is never called by the PEAR code. Attached patch removes this 'historical' check, replacing it by a check for class type. (also updates some 'historical' documentation in it) (should be able to still make 1.5.2 ?) g,T


 [2007-04-09 01:49 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the 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.
 [2007-04-09 01:50 UTC] cellog (Greg Beaver)
This patch needs to be implemented in HEAD as well as PEAR_1_5