I disagree strongly. I wouldn't like to count the number of times I've
had calls from users trying to follow examples in manuals which use
non-typewriter (or worse, mixed-font) faces for code samples. Typically
the users are in despair, saying "I'm trying to type in the example,
but every time I try to type a word in bold or italics, it won't let
me|rejects what I type|beeps at me". The assumption that users,
particularly novices, are capable of automatic interpretation of the
semantics of font usage in examples is, I'm afraid, wholly false. It
is utterly crucial that examples should be wholly unambiguous, even if
this does mean catering for the less able reader, and unfortunately
right now this means lowest-common-denominator fixed-width TTY.
> Code should
> be styled in a way appropriate to its language, which means you should
> have types (or classes) like KEYWORD, VARIABLENAME, LIBRARYROUTINENAME,
> etc.
Its use in a book designed for experienced users is perhaps justified.
///Peter