From -7459116332855098404
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,4aa07bccd99d934b,start
X-Google-Attributes: gidf78e5,public
From: "Scott Robert Ladd" <srladd@frontier.net>
Subject: Suggestions for improving the *Obtuse* Standard
Date: 1999/06/25
Message-ID: <930235591.934.103@news.remarQ.com>#1/1
X-Deja-AN: 493630950
Approved: Valentin Bonnard <bonnard@clipper.ens.fr>
X-Original-Date: Thu, 24 Jun 1999 08:47:09 -0600
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Organization: Posted via RemarQ, http://www.remarQ.com - The Internet's Discussion Network
X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBVAwUAN3L6nqwEuYhIxRhxAQHPHgH8CNWPKcKryOYwGIYAONhVNV+0lvwqKLg9 ekgaBTLoQqcs+tCMV2UhNa5FU+kq7oFDeMlUEok8jXY9PdjQwVhP9g== =iZVt
X-MSMail-Priority: Normal
Newsgroups: comp.std.c++

To begin with, my use of the word "obtuse" was quite correct. My Webster's
10th Collegiate defines one meaning for obtuse as: "Difficult to comprehend:
not clear or precise in thought or expression." And that is exactly what I
meant to say. I suggest some people might want to consult their dictionaries
before criticizing someone else's English, much as they expect people to
consult the Standard before asking questions about C++.

Please take the following in the light of constructive criticism from
someone who does not have an emotional connection to the Standard. I respect
the work of the Committee.

Be that as it may, I believe that the Standard would be most improved by its
reorganization into a well-designed hypertext document, linking related
sections to provide a better presentation of complete concepts. I could, if
anyoen is interested, work up an example.

To the extent possible, the library section should be separated into a
different document. The language itself is largely (but not completely, as
evidence by the discussion of "new") a separate issue from the class
library. This is especially true of the Standard implementation of
containers. I think the document lacks focus; division would allow separate
subcommittees to concentrate on specific sections of the document.

The document should also include the relevent sections of the C standard;
the C++ Standard appears to assume that its readers are experienced C
programmers -- and that is a disservice in today's world, where programmers
often *begin* with C++.

I don't like the typography, especially in the library section. Members
should be "outdented", text regarding them indented, with better use of
fonts to highlight the document's structure.

Are those specific enough, Pete? ;}

--
    Scott Robert Ladd
    Coyote Gulch Productions
    srladd@frontier.net
    http://www.frontier.net/~srladd
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]



