This article is from the Object-Oriented Technology FAQ, by Bob Hathaway firstname.lastname@example.org with numerous contributions by others.
From: email@example.com (Neil Wilson)
Subject: New version of 'short' available
Date: Sat, 7 Aug 1993 09:38:25 +0000
A new beta release (1.2) of 'short' is available from the Stuttgart
Eiffel archive (ftp.informatik.uni-stuttgart.de) in directory
Command line processing is now included in the short system. Short can
now cope with multiple input files, the standard input and deal with
most file errors.
Short now depends on the argument cluster which is available from
the same archive and directory.
Short supports the following options:
-V, +version, -h, +help
Displays the 'short' version information and gives the
usage help message for the command.
-e, +abstract, +eiffel
Produces a fully deferred version of the input class(es)
which will compile just like any other class (hopefully :-)
-l <class_name>, +view <class_name>
Produces the output from the point of view of the class
<class_name> - the "short form for <class_name>".
Special handling for ANY and NONE of course. By default
short outputs the "short form for ANY".
Produces the short form including all the feature
blocks. (Implemented as the "short form for NONE".)
Retains the inheritance clause in the output. The default is
to drop it.
-b <number>, +blank <number>
Indent levels by <number> characters.
-c <number>, +column <number>
Width of the output is <number> characters. Should be
greater than 20.
Obsolete features are not retained. Obsolete classes retain no features.
The output of the tool now conforms to the layout rules in Appendix A of
ETL and should look like the 'short' examples in the book. As much as is
possible the output and command line options conform to ISE's 2.3
version of 'short'.
This release of short has been tested on all the v1.21 Eiffel/S
libraries, itself and the argument clusters, plus any other class
fragments I had lying around at the time.
My biggest debt is of course to David Morgan. This version is only
really a tiny modification of his work. His ELEXER Eiffel 3 parser
remains the core of the tool. I though am responsible for any remaining
deficiencies or problems with this release.
Problems, suggestions, comments, criticisms to me please. All gratefully
received - I can't improve my Eiffel if somebody doesn't tell me where I