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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: 
 border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "G.B." <bauhaus@futureapps.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Is there a way to do large block of source code comments
Date: Thu, 04 Sep 2014 17:44:50 +0200
Organization: A noiseless patient Spider
Message-ID: <lua1di$4fn$1@dont-email.me>
References: <f6d1bf8f-cede-435e-9a12-ebae61ea95ca@googlegroups.com>
 <lu2fvl$5kc$1@dont-email.me>
 <8fd27434-43c2-4bd1-b72b-dd7a0ef5af75@googlegroups.com>
 <cwGNv.139297$w82.70721@fx21.iad>
 <65680926-cda9-40a6-8f45-3a1f80452020@googlegroups.com>
 <lu93sg$nke$1@dont-email.me>
 <26b20ef5-fbbb-4a5c-8ea7-3c61233cb858@googlegroups.com>
Reply-To: nonlegitur@futureapps.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 4 Sep 2014 15:44:51 +0000 (UTC)
Injection-Info: mx05.eternal-september.org;
 posting-host="b96887e80893c84a90c3007226ca0d1c";
 logging-data="4599"; mail-complaints-to="abuse@eternal-september.org";
 posting-account="U2FsdGVkX18D6GzKk33fe92BPXeyIFdJPABMTAxAX+c="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
In-Reply-To: <26b20ef5-fbbb-4a5c-8ea7-3c61233cb858@googlegroups.com>
Cancel-Lock: sha1:Ql4XH727WV4klsiXme6x5HdajTA=
Xref: number.nntp.dca.giganews.com comp.lang.ada:188867
Date: 2014-09-04T17:44:50+02:00
List-Id: <comp.lang.ada>

On 04.09.14 14:46, robin.vowels@gmail.com wrote:
> On Thursday, September 4, 2014 5:20:49 PM UTC+10, Georg Bauhaus wrote:
>> On 04.09.14 04:37, r.nospam@gmail.com wrote:
>>
>>> Um, comments highlighted in a different color from the code
>>
>>> make it clear which is commented.
>>
>>
>>
>> But highlighting doesn't make it clear what the "commented" text
>> is about,
>
> Just read the comment.

It is an onerous job of a programmer to spend payed time on
guessing the reasons that some lazy (or deprived) typist
has had when turning a large part of source text into a
"comment". More guesswork for both the IDE and the compiler,
in the presence of the usual pitfalls of multiline comment
indicators, will not help.  But, since you were switching use
cases ...

>> the current reader (human debugger, reviewer, successor) frequently
>> needs to understand it. (*)
>
> Knowledge of English would help.

... to natural language comments... Why was having YX ...PROSE
... YX technically superior for writing natural language comments?

>> Using comment indicators for disabling some source text is
>> the original sin.
>>
>> However, since the practice of "quickly disabling" a part of
>> the source text during coding is commonplace,
>
> And, I might add, during program testing, and in finding bugs in the compiler.

Oh. Now back to use case "disabled source text"... Where you
said that XY ... XY is convenient. Not for the team, as outlined.


I'd agree that "elegance" is subjective and makes the Rationale
sound like marketing jargon in "combining elegance with safety"
when addressing rather primitive aspects of comment syntax.
That still does not invalidate its technical arguments.