Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c++ > #118875 > unrolled thread

Re: Reading specs (How to)

Started byTim Rentsch <tr.17687@z991.linuxsc.com>
First post2024-04-24 12:26 -0700
Last post2024-04-24 12:26 -0700
Articles 1 — 1 participant

Back to article view | Back to comp.lang.c++

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Reading specs (How to) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-04-24 12:26 -0700

#118875 — Re: Reading specs (How to)

FromTim Rentsch <tr.17687@z991.linuxsc.com>
Date2024-04-24 12:26 -0700
SubjectRe: Reading specs (How to)
Message-ID<86sezawoi6.fsf@linuxsc.com>
ram@zedat.fu-berlin.de (Stefan Ram) writes:

>   How many of you have read through the C++ spec, like, all the
>   way through?
>
>   Have you guys checked out the latest version of the C++ spec yet?
>
>   I was just browsing around and I stumbled upon this little
>   guide in the WHATWG HTML spec on how to properly read through
>   these kinds of technical specifications!
>
> |1.9.1 How to read this specification
> |
> |This specification should be read like all other
> |specifications.  First, it should be read cover-to-cover,
> |multiple times.  Then, it should be read backwards at least
> |once.  Then it should be read by picking random sections from
> |the contents list and following all the crossreferences.
> |
> HTML Living Standard - Last Updated 9 April 2024

Any document that includes such advice is giving a tacit
acknowledgement that what is being described is poorly
designed or that the describing document is poorly written,
or both.

[toc] | [standalone]


Back to top | Article view | comp.lang.c++


csiph-web