search for: xmlblog

...allowed To: noreply at rubyforge.org Feature Requests item #5856, was opened at 2006-09-22 17:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=7480&aid=5856&group_id=1917 Category: None Group: None Status: Open Priority: 3 Submitted By: Christian Romney (xmlblog) Assigned to: Nobody (None) Summary: Stubbing of private methods should be allowed Initial Comment: I have a private method in my Rails controller that does some processing. Based on the return value of this method, a particular action decides what to do. I do not want to make this method public,...

Hi all, I realize this behavior is by design, and in some respects the right thing to do. It also pre-dates the addition of Enumerable#count. I''m wondering, however, if it''s possible/desirable to allow the caller to access the Enumerable versions under certain conditions. I originally wrote the up as an issue, but was informed this would be the better venue. I''m

Hi all, I found this thread in the August backgroundrb-devel archives. >This means that in order to reference the new_worker method *in the >instance that is running in the drb server* you can''t do that >directly. In order to spawn other workers from within a worker I >would have to change the MiddleMan class to be a singleton. This way >you could grab the one instance of

Ok let this be a lesson to the general public. If you want to look as idiotic as I do right now do the following: Stay up all night and attempt to debug code the next day without coffee Patch the wrong file RAILS_ROOT/scripts/backgroundrb/start instead of one in plugin dir. Create a patch in the right location containing nothing but an extra space Send it to the whole Ruby community AND file a