From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Path: eternal-september.org!reader02.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!cleanfeed2-b.proxad.net!nnrp1-1.free.fr!not-for-mail
Newsgroups: comp.lang.ada
References: <5fdbde31$0$6455$426a74cc@news.free.fr>
 <86im8ylnj4.fsf@stephe-leake.org> <5fdde913$0$3238$426a74cc@news.free.fr>
 <86eejllb14.fsf@stephe-leake.org>
From: DrPi <314@drpi.fr>
Subject: Re: Ada syntax questions
Date: Sun, 20 Dec 2020 15:10:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <86eejllb14.fsf@stephe-leake.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <5fdf5b68$0$4023$426a34cc@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 20 Dec 2020 15:10:48 CET
NNTP-Posting-Host: 82.65.30.55
X-Trace: 1608473448 news-4.free.fr 4023 82.65.30.55:64470
X-Complaints-To: abuse@proxad.net
Xref: reader02.eternal-september.org comp.lang.ada:60901
List-Id: <comp.lang.ada>

Le 19/12/2020 à 22:51, Stephen Leake a écrit :
> DrPi <314@drpi.fr> writes:
> 
>> Reading the code can't tell you the writer's intentions.
> 
> That's what comments and design documents are for.
> 

A good IDE with code analysis showing you object declaration/use is very 
useful. Especially when comments are out of sync with the code.

I'm surprised that no modern tool/language allows the programmer to 
embed a "complete" documentation in source files.
I'm not talking about comments formatted to suit a specific tool 
convention, like Python or Perl doc-strings.
I' talking about embedding schematics, drawings, bitmaps, mathematical 
equations, etc directly in the source code.
Or maybe the reverse : embed source code in standard document. Like 
javascript in SVG files.
Why not a .odt file with code sections ? Ok, a specific file format 
would be better.
Of course, the editor should be specific. Not more a simple text editor.