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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 Path: border1.nntp.dca1.giganews.com!nntp.giganews.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!fx31.iad.POSTED!not-for-mail From: Shark8 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:34.0) Gecko/20100101 Thunderbird/34.0a1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Is there a way to do large block of source code comments References: <8fd27434-43c2-4bd1-b72b-dd7a0ef5af75@googlegroups.com> <65680926-cda9-40a6-8f45-3a1f80452020@googlegroups.com> In-Reply-To: <65680926-cda9-40a6-8f45-3a1f80452020@googlegroups.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Message-ID: X-Complaints-To: abuse@teranews.com NNTP-Posting-Date: Fri, 12 Sep 2014 01:51:52 UTC Organization: TeraNews.com Date: Thu, 11 Sep 2014 19:52:00 -0700 X-Received-Bytes: 3611 X-Received-Body-CRC: 1829394845 X-Original-Bytes: 3628 Xref: number.nntp.dca.giganews.com comp.lang.ada:188974 Date: 2014-09-11T19:52:00-07:00 List-Id: On 9/3/2014 7:37 PM, robin.vowels@gmail.com wrote: > On Thursday, September 4, 2014 1:32:21 AM UTC+10, Shark8 wrote: >> On 02-Sep-14 18:07, r.nospam@gmail.com wrote: >> >>>> No, this was explicitly omitted. See the Ada-83 Rationale 2.1: "Single comments >> >>>>> that are larger than one line are not provided. Such comments would require a >> >>>>> closing comment delimiter and this would again raise the dangers associated with >> >>>>> the (unintentional) omission of the closing delimiter: entire sections of a >> >>>>> program could be ignored by the compiler without the programmer realizing it, so >> >>>>> that the program would not mean what he thinks. Long comments can be written as >> >>>>> a succession of single line comments, thus combining elegance with safety." >> >>> >> >>> The above quotation is mere hype, like the author's justification for omitting >> >>> exponentiation in Pascal, somehow more convenient to use log and exp instead! >> >> No, the above is a quotation from the Ada Rationale. > > But it's still hype. hype verb (used with object), hyped, hyping. 1. to stimulate, excite, or agitate (usually followed by up): 2. to create interest in by flamboyant or dramatic methods; promote or publicize showily: a promoter who knows how to hype a prizefight. 3. to intensify (advertising, promotion, or publicity) by ingenious or questionable claims, methods, etc. (usually followed by up). 4. to trick; gull. noun 5. exaggerated publicity; hoopla. 6. an ingenious or questionable claim, method, etc., used in advertising, promotion, or publicity to intensify the effect. 7. a swindle, deception, or trick. ----- I really don't see how it's hype. What definition are you using? >> It says that only single-line comments terminated by the end of the line >> were chosen so that there was no way that closing a multiline comment >> could be forgotten. Period. >> >>> Live parsing editors are useful tools, because they highlight >>> code segments (including comments). >> >> What has this got to do with *anything* WRT comments? > > Um, comments highlighted in a different color from the code > make it clear which is commented. > So? If that's the be-all / end-all of your editor then it's no wonder CS is in such a horrid state -- editors 'understanding' syntax and semantics well enough for syntax-highlighting is a pretty low bar. I suggest you read up on research on things like DIANA and the R-1000 (80's tech) which will illuminate you on just how poorly tool development has progressed [regressed?] over the past several decades.