It should be possible to use a CallBag or a CallSequence wherever you can
use a Call. That is, you should be able to have a bag of sequences or a
sequence of bags, with single-shot calls mixed in as well. If that is not
possible, then I would consider that a bug.
_______________________
Dr. Nathaniel Pryce
B13media Ltd.
http://www.b13media.com
+44 (0)7712 526 661
----- Original Message -----
From: <st...@m3...>
To: <moc...@li...>
Cc: <st...@m3...>
Sent: Tuesday, June 10, 2003 11:19 AM
Subject: Re: [MO-java-dev] CallBag is a Callable?
> I'm worried that we'll refactor out flexibility that will be very
difficult
> to put back in when somebody needs it. The previous version of the
dynamic
> mocks was a little too inflexible, and mock objects created by the core
> library are very inflexible and need to be modified too frequently.
>
> The idea of making CallBag and CallSequence implement Call is to find a
> happy medium between the simplicity of sequences or choices of expected
> calls and the over-complexity of state machines.
In which case, perhaps we should distinguish between Callable and Matchable?
To me, the current situation is confusing because we have 2 implementations
that will fail if you try to use them as Callables.
S.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Mockobjects-java-dev mailing list
Moc...@li...
https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
|
