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

Bug #10784 Net_IDNA::singleton() calls non-existant factory() method
Submitted: 2007-04-20 03:35 UTC
From: aharvey Assigned: neufeind
Status: Closed Package: Net_IDNA (version 0.7.1)
PHP Version: 5.2.1 OS: Irrelevant
Roadmaps: (Not assigned)    
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 : 9 + 1 = ?

 
 [2007-04-20 03:35 UTC] aharvey (Adam Harvey)
Description: ------------ Net_IDNA::singleton() calls ::factory(), rather than ::getInstance(). The attached patch is against 0.7.1. Test script: --------------- <?php include 'Net/IDNA.php'; $idna = &Net_IDNA::singleton(); ?> Expected result: ---------------- No output. Actual result: -------------- Fatal error: Call to undefined method Net_IDNA::factory() in / usr/share/pear/Net/IDNA.php on line 92 Call Stack: 0.0003 1. {main}() /tmp/test.php:0 0.0011 2. Net_IDNA::singleton() /tmp/test.php:3

Comments

 [2008-03-22 13:29 UTC] neufeind (Stefan Neufeind)
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.
 [2008-10-25 07:56 UTC] doconnor (Daniel O'Connor)
This is not fixed in CVS.
 [2008-10-25 08:34 UTC] kguest (Ken Guest)
I can confirm this is not fixed in CVS.
 [2009-07-24 10:17 UTC] doconnor (Daniel O'Connor)
-Status: Assigned +Status: Closed
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.