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=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.50.66.236 with SMTP id i12mr2396464igt.5.1409834779318;
 Thu, 04 Sep 2014 05:46:19 -0700 (PDT)
X-Received: by 10.50.134.3 with SMTP id pg3mr68954igb.4.1409834779223; Thu, 04
 Sep 2014 05:46:19 -0700 (PDT)
Path: 
 border1.nntp.dca1.giganews.com!nntp.giganews.com!uq10no9349793igb.0!news-out.google.com!ef6ni1411igb.0!nntp.google.com!r2no14207114igi.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 4 Sep 2014 05:46:18 -0700 (PDT)
In-Reply-To: <lu93sg$nke$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=123.2.70.40;
 posting-account=S_MdrwoAAAD7T2pxG2e393dk6y0tc0Le
NNTP-Posting-Host: 123.2.70.40
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>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <26b20ef5-fbbb-4a5c-8ea7-3c61233cb858@googlegroups.com>
Subject: Re: Is there a way to do large block of source code comments
From: robin.vowels@gmail.com
Injection-Date: Thu, 04 Sep 2014 12:46:19 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: number.nntp.dca.giganews.com comp.lang.ada:188863
Date: 2014-09-04T05:46:18-07:00
List-Id: <comp.lang.ada>

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.

> and how it is structured.  Since the text is still there,

One would hope that the comment contains some text!

> the current reader (human debugger, reviewer, successor) frequently
> needs to understand it. (*)

Knowledge of English would help.

> 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.

> languages could
> as well start supporting that! Specifically support that, I mean,
> not via generic comments. It needs to be the language, because the
> tools would have to be at least as good as the compiler and its
> error handling code. But current tools tend not to be language
> specific.
>
> Another technique that may do during coding, provided that there
> are no far reaching declarations that will vanish:
>
>    if False then
>       as_if (commented);
>       here_as (well);
>    end if;
> 
> The effect on a future reader will be just as annoying as a
> "commented multiline section" of code. Fans of editors may
> use folding to hide either from sight.