Re: [NMock2-Dev] Fire syntax

[Steve M. <Ste...@ty...>]

They are related in that they are actions that could be 'caused' by a
call to a mocked method.=20

-----Original Message-----
From: nmo...@li...
[mailto:nmo...@li...] On Behalf Of Andrey
Shchekin
Sent: Saturday, October 13, 2007 3:50 PM
To: NMock2 Development Discussion
Subject: Re: [NMock2-Dev] Fire syntax

On 10/14/07, Steve Mitcham <Ste...@ty...> wrote:
> That's why I used 'Cause' instead of set,  I'm pretty sure that set
> isn't a collision in any namespace.   Importing the NMock2 namespace
is
> just a convenience.  There's nothing from stopping anyone from not
> 'using' the NMock2 namespace and typing:
>
> NMock2.Cause.Parameter(1).ToBe("Foo");
>
> I do, however, want to avoid obvious collisions like 'Set'

What about Change.Parameter(1).To("Foo")?

I think ToBe is harder than To to type and to remember.
And is there actually a need to group event raising and parameter
changing in single class? These concepts seem quite unrelated to me.

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NMock-two-dev mailing list
NMo...@li...
https://lists.sourceforge.net/lists/listinfo/nmock-two-dev