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

Request #5021 SVN objects are not reusable
Submitted: 2005-08-07 16:46 UTC
From: mihamix at openttd dot org Assigned: clay
Status: Closed Package: VersionControl_SVN
PHP Version: Irrelevant OS: All
Roadmaps: 0.3.1    
Subscription  
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes. If this is not your bug, you can add a comment by following this link. If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
2007-09-17 18:33 UTC
Package:
Bug Type:
Summary:
From: mihamix at openttd dot org
New email:
PHP Version: Package Version: OS:

 

 [2005-08-07 16:46 UTC] mihamix at openttd dot org
Description: ------------ If I create a VersionControl_SVN_List via a $svn = VersionControl_SVN::factory(array('list'), $options); call, I got an object, which I can call: $svn->list->run($args, $switches); If I call this object multiple times with different $args, it'll still executes the first call, since: VersionControl/SVN.php line 616 and later: if (!$this->_prepared) { $this->prepare(); } It's obvious, that it'll only prepare at the first time, so it makes difficult (if not impossible) to reuse the above object (since $_prepared 'declared' as private (it's ok). Would it be possible to raise this limitation, and allowing users to reuse the $svn object?

Comments

 [2005-08-07 16:58 UTC] mihamix at openttd dot org
I've created a small patch, which will solve the whole problem. I've uploaded it to here: http://xenon.bibl.u-szeged.hu/~miham/php/svn.diff It's maybe ugly, but the whole conception works good.
 [2007-09-17 18:33 UTC] clay (Clay Loveless)
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.