// @(#)$Id: exercise.txt,v 1.1 1995/09/14 18:37:48 leavens Exp $

If you haven't already read chapters 1-3 of
``Larch: Languages and Tools for Formal Specification''
by John V. Guttag, James J. Horning, et al. (Springer-Verlag, 1993),
please do so before continuing.  This gives some background, and
an overview of the role of the Larch Shared Language (LSL)
in writing interface specifications.
(You might also want to read section 1.1 of the Larch/C++ Reference manual.)

Now consider the following questions.

1. Why is it important to have some familiarity with LSL
   in order to write or read Larch-style interface specifications?

2. Given that Larch/C++, like Larch/C (LCL) and Larch/Modula-3 (LM3)
   is an interface specification language, how would you describe
   the role of LSL in Larch/C++ specifications?