In Inform's acase, any ambiguities can be resolved by reading the
libraries, but for some people (i.e. me) that is a frightening prospect.
I would be more than happy to contribute to the improvement of the
manual. I like the way Graham Nelson described it in the introduction:
"[some parts] are both leaden _and_ patronizing". The style of it is
excellent and just feels right for the subject.
Some manuals simply attempt to describe the syntax of the language,
whereas others try to describe what can be done, and hope that the syntax
shows through. It's like reading a book on C++ vs. a book on
object-oriented programming. I think the Designers' Manual does both
simultaneously and it doesn't always work.
I reiterate: I'm more than willing to help out in the manual's
development. If there were an IF game for learning programming, I'd have
5 out of 100 points, 100 being the skill for a finished game, giving me
the ranking of doe-eyed, frightened rookie.
/Steve