It's not on the current radar but it can certainly be looked into while
refactoring the code base
On Tuesday, September 17, 2013 10:00:58 AM UTC-4, Tarpan wrote:
>
> Mike, any plans to fix this bug any soon?
>
>
> On Wednesday, July 10, 2013 4:03:45 PM UTC-4, Tarpan wrote:
>
>> Hi all,
>>
>> I cannot make "Do" work in the same sentence with "Ref" because "Ref"
>> takes a second argument "ReturnValue" and passes it into "Do". As so "Do"
>> cannot get access to the original value of the argument.
>>
>> Here is the example (forgive some syntax errors, don't have Visual Studio
>> with me)
>>
>>
>> var stub = MockRepository.GenerateStub<MyInterface>();
>> stub.Stub(x => x.Method(Arg<DataTable>.Ref(Is.Anything(), *null*
>> ).Dummy)).Do(DoAction)
>>
>> ...
>>
>> private void DoAction(DataTable table)
>> {
>> // guess what? table is always *null *!
>> }
>>
>>
>> Anybody had the same issue before? Please help.
>>
>> Why ReturnValue is a required parameter? It should be optional.
>>
>> Alex
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Rhino.Mocks" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rhinomocks.
For more options, visit https://groups.google.com/groups/opt_out.