RE: saving state between fixtures

Micah,

> > Other than that, I think the location is exactly correct - a 
> > second hash
> > in Fixture that would allow storing state would be exactly correct. In
> > fact, using a hash opens up the intreguing idea of using it 
> > as a symbol
> > table.
> > 
> 
> This is what I suggested a while back.  Michael Feathers made a good
> point.... How is this done in C++ where there is no common Object base
> class?  

You could limit state to strings, use void*, use template functions or
classes, require the client to do a dynamic_cast<> or some combo of
the above. What's the minimum function that should be available to all
implementations? Should implementations that support it get more function?

Charlie Poole
[email protected]
www.pooleconsulting.com
www.charliepoole.org