Page 10	Table of Contents	Index	Page 12
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E

---

CHAPTER 2. CONVENTIONS

• If this situation does occur, the effects and results are undefined as far as adherence to the
  CLIM specification is concerned.
  
• CLIM implementations are not required to detect such an error, although implementations
  are encouraged to provide such error detection whenever it is reasonable to do so.

When this specification specifies that some argument "must be a type" or uses the phrase "the
type argument", this means that it is an error if the argument is not of the specified type. CLIM
implementations are encouraged, but not required, to generate an argument type error for these
situations.
When this specification says that "an error is signalled" in some situation, this means that:

• If the situation occurs, an error will be signalled using either error or cerror.
  
  
• Valid CLIM programs may rely on the fact that an error will be signalled.
  
  
• Every CLIM implementation is required to detect such an error.

When this specification says that "a condition is signalled" in some situation, this is just like "an
error is signalled" with the exception that the condition will be signalled using signal instead
of error.

---

Page 10	Table of Contents	Index	Page 12
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E