[Mockobjects-java-users] Avoiding loops in Verifier again.

[Steve F. <st...@m3...>]

I've done a little tidy up in the Verifier. No major functional changes yet,
but I've made verifyField() private  -- unless someone wants it back.

That static vector still gets up my nose, I've done some refactorings
towards getting away from it but got a bit stuck, so I'd like to poll people
again.

It seems that the principal need for this is in the JDBC library where, for
example, a mock statement references a mock connection and vice versa. I
can't help feeling that we've let our desire for generality get out of hand
and that we really shouldn't be writing code that daisy-chains statements
and connections (or whatever). Similarly, I doubt that we should have one
setup routine for a "cluster" of related objects, we should have several to
implement multiple situations.

I'd like to propose that a Verifiable loop is a code smell which implies
that something has become too complicated, so we shouldn't compensate for
it.

Thoughts?

Steve

- - - - - - - - - - - - - - -
Steve Freeman   st...@m3...
Programme chair OT2003. http://www.ot2003.org

"Nonsense is just nonsense, but the study of nonsense is science."