> What we need is not just a bigger dictionary of Oberon/F, although that might
> be helpful: what we need is a thesaurus, and a copy of Bartlett's Quotations.
> We need a document explaining, in detail, with clear examples, the large
> number of messages sent and received by the framework. We need an expanded
> repertoire of templates for the subsystem source code generator. A book
> comparable to Hanspeter Moessenboeck's Object-Oriented Programming in
> Oberon-2, but using Oberon/F, would be ideal.
I agree. What I need is an explanation of the meta programming
rules of the framework more that a description of the behavior
of the modules. I heard that an Oberon/F specific book was in
the works. Perhaps someone at OMI could tell us the status of
that book.
Stan Warford
Pepperdine University
warford@pepperdine.edu