Every software system has, beyond its formal sematics, a set of pragmatics: Assumptions on how the system will be used that affect how it is implemented.
Use the system as intended and it will be reasonably effective and efficient.
Use it in unanticipated ways, and you are likely to find the implementation inefficient and ineffective.
The purpose of this section is to give you some notion of what sort of coding practices and problems the Muq implementation was designed to handle. You don't have to limit yourself to these, of course, but at least you'll know when you are venturing into deep water.
Go to the first, previous, next, last section, table of contents.