Path: csiph.com!news.mixmin.net!border2.nntp.ams1.giganews.com!nntp.giganews.com!buffer2.nntp.ams1.giganews.com!buffer1.nntp.ams1.giganews.com!nntp.brightview.co.uk!news.brightview.co.uk.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 18 Nov 2016 06:34:23 -0600
From: Gareth Owen <gwowen@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Experimental languages/features for C or similar
References: <49bb22bc-7863-4b60-9685-4706e4df93eb@googlegroups.com> <70398b95-088c-4936-9073-aafcb872d892@googlegroups.com> <o047ch$2av$1@dont-email.me> <o0kvjd$ung$1@dont-email.me> <ln37ipho79.fsf@kst-u.example.com> <o0l7b3$s29$1@dont-email.me> <lntwb5g2qv.fsf@kst-u.example.com> <o0ldgt$kl5$1@dont-email.me> <o0m9qk$ihv$1@dont-email.me> <o0mlti$mr3$1@dont-email.me> <o0mrda$art$1@dont-email.me>
Date: Fri, 18 Nov 2016 12:34:22 +0000
Message-ID: <87zikx6k6p.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Cancel-Lock: sha1:6tMKqn0rMUC2un3qLCvKCRPR9gM=
MIME-Version: 1.0
Content-Type: text/plain
Lines: 32
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-Nxxym3KooYBDJK91G5gPzDE6/YcLJ8wo6HU7FFKDlvjyzTgTmijkCndFVHyDbTF3qcp7NY0bCXOGXLD!MQckmpKIoPtRkjEpz+0cc7XT0KV51HDqQrMC3/U+leoDprI4tZ+kllPzIy5fajRA+QJC
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2933
Xref: csiph.com comp.lang.c:96812

David Brown <david.brown@hesbynett.no> writes:

>> I wrote the C containers library and an EXTENSIVE TECHNICAL
>> DESCRIPTION of all the specs and code that I published. Look at the
>> PDF file and you will see what I consider a technical documentation.
>
> The CCL documentation (I recommend you use the hyperref package when
> generating the pdf - it will give the pdf a proper table of contents
> and clickable links.  Other than that, the document looks very
> impressive) is a mixture of a tutorial on CCL and a reference for how
> to use the library.  gcc does not come with a reference on the
> programming languages it implements (the ISO standards, or their
> drafts, are available elsewhere), nor is it a tutorial on C
> programming.

No, it does not.  But some equally awful terrible very-bad free software
people do maintain CPP reference (http://en.cppreference.com/) which
documents the C++ standard library every bit as well as Jacob documents
his library.

And of course, its fatuous to compare the quality of documentation for a
library (which is absolutely crucial for library end users) and the
documentation of the internals of a compiler (which is utterly
irrelevant for compiler users).

And, of course, whether the documentation for the internals of LCC is
good or not is even more irrelevant, only a very small number of people
needs to see it, wishes to see it, or is allowed to see it.

The documentation for writing a new front-end for gcc may be deficient,
but its *still* easier for me to write a new front-end for gcc than it
is to write one for lcc.