On 2009-12-03 23.27, Niclas Hedhman wrote:
Hi, I was just referring to post-conditions as a platform for discussion at a theoretical level. I am not very good with UML either, but vaguely recall that pre-conditions mapped more or less 1-1 with our constraints.
No, pre-conditions are about internal state and constraints are about incoming state/parameters. Check the Wikipedia page:
http://en.wikipedia.org/wiki/Use_case
@Identifier String identifyNextToken(); Secondly, in-argument constraints are really a tool to ensure that "users" of a piece of code doesn't throw invalid values at it. What is the primary purpose of out value checks? As a documentation tool to such user it would be great, but does it really help if there is a violation in runtime, which would indicate an internal error (bug) in the codebase that one uses. Is it worth the runtime overhead of such constant checks? Or is it simply a matter of a giant Qi4j.enablePostConstraints( boolean on ) switch?
Good question. What are the usecases for return-value constraints, really? /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
