From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,9124c8b7efcea462
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!postnews.google.com!k17g2000yqb.googlegroups.com!not-for-mail
From: sjw <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada and Doxygen
Date: Fri, 26 Feb 2010 23:46:24 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <ee008b57-026d-414e-93b0-8a409864cfcf@k17g2000yqb.googlegroups.com>
References: <op.u8mib9tdvwnd5a@garhos>
 <4b84fb09$0$6579$9b4e6d93@newsspool3.arcor-online.net>
	<op.u8mpsskzvwnd5a@garhos> <u7hq1y0e5.fsf@stephe-leake.org>
	<op.u8oug5xjvwnd5a@garhos> <umxywwfef.fsf@stephe-leake.org>
	<45d5f4b8-8e8e-43ef-94df-0558262cd978@g11g2000yqe.googlegroups.com>
	<op.u8q0iomjvwnd5a@garhos>
 <68cf6a9d-240b-4970-98f0-fee32795f00d@e7g2000yqf.googlegroups.com>
NNTP-Posting-Host: 82.30.110.254
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1267256784 29928 127.0.0.1 (27 Feb 2010 07:46:24
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 27 Feb 2010 07:46:24 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: k17g2000yqb.googlegroups.com; posting-host=82.30.110.254;
	posting-account=_RXWmAoAAADQS3ojtLFDmTNJCT0N2R4U
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-us)
	AppleWebKit/531.21.8 (KHTML,
 like Gecko) Version/4.0.4 Safari/531.21.10,gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:9336
Date: 2010-02-26T23:46:24-08:00
List-Id: <comp.lang.ada>

On Feb 26, 8:04=A0pm, Vadim Godunko <vgodu...@gmail.com> wrote:

> Qt's uses another way. There are no comments in headers at all. This
> makes header files clean - it is very important for overview of the
> class. All comments are placed in the implementation files. Special
> tool parse both headers and implementation files, construct list of
> classes, its methods/signals/slots/etc; then parse implementation
> files and extracts description for each entity; links classes/methods/
> slots/signals with their descriptions and construct complete
> documentation in HTML form, which can be hosted somewhere or read by
> browser. After that, another tool pack this documentation and all
> related resources into the one "database" which can be registered in
> the Qt Assistant to extend useful of it (Qt Assistant allows to do
> full text search for example). And even it is not a last step, when
> you use Qt Creator (IDE for Qt) and stay somewhere in the code, you
> can click key and Qt Creator opens description of class/method you
> stay on in the Qt Assistant documentation. It is very fast and useful!

I think you're saying that humans never need to read the .h files at
all, because tools make it possible to read the documentation where/
when you need to, in whatever form is most appropriate.

Nothing wrong with the outcome, but (it seems to me that) if the Qt
scheme had started from having full descriptions in the .h files and
the tools worked in that environment instead, you would be in
*exactly* the same position as now.

I find it frustrating going from the package specs in the LRM to
somewhere down-page which describes what the code actually means.