From: John Maddock (John_Maddock_at_[hidden])
Date: 2001-07-19 06:58:17
>* Clearly identify the actual hard requirements in a separate document.
Or use colour coding in the document to highlight the difference between
"do this" and "this is a good idea, but don't follow if you don't want to",
rather like the way that the draft POSIX v6 standard highlights optional
BTW I think that the coding guidelines should be hosted at boost, I don't
necessarily agree with all of the choices, but on the whole I like these
guideline very much indeed, well done!
- John Maddock
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk