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=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,429176cb92b1b825
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news2.google.com!news4.google.com!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!.POSTED!not-for-mail
From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?=
 =?utf-8?Q?=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: AWS Coding Styles (and about boring plain-linear text files in
 the end)
Date: Wed, 16 Mar 2011 19:28:29 +0100
Organization: Ada @ Home
Message-ID: <op.vsf79rhwule2fv@index.ici>
References: <op.vpfsjkfdule2fv@garhos>
 <24418fa4-8843-4fe6-8c2f-026ea6009b68@g26g2000vbz.googlegroups.com>
 <87lj2ido9j.fsf@mid.deneb.enyo.de> <4D35F6C8.2060100@obry.net>
 <4d3608ab$0$7664$9b4e6d93@newsspool1.arcor-online.net>
 <ih539t$7e4$1@munin.nbi.dk>
 <4d3634a5$0$7664$9b4e6d93@newsspool1.arcor-online.net>
 <op.vpi6pgmlule2fv@garhos>
 <4d36b748$0$6977$9b4e6d93@newsspool4.arcor-online.net>
 <op.vpjz4nfaule2fv@garhos>
 <4d36e484$0$6769$9b4e6d93@newsspool3.arcor-online.net>
NNTP-Posting-Host: nCoynSItJacK8nNC7nzOHA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/11.01 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: g2news2.google.com comp.lang.ada:19221
Date: 2011-03-16T19:28:29+01:00
List-Id: <comp.lang.ada>

Le Wed, 19 Jan 2011 14:17:56 +0100, Georg Bauhaus  =

<rm.dash-bauhaus@futureapps.de> a =C3=A9crit:

> On 19.01.11 12:42, Yannick Duch=C3=AAne (Hibou57) wrote:
>
>> According to the authoritative FunnelWeb documentation, which you can=
  =

>> access
>> here:
>> http://www.ross.net/funnelweb/tutorial/intro_hello.html
>> the body of a macros, whose purpose is to expand into program text, i=
s  =

>> exactly
>> the same as the one you suggested!
>
> No, no, the brackets @{ @}, or the line-of-code indicator @@ are much
> simpler than FunnelWeb.  For one thing, the Ada programmer only needs
> to understand Ada and  will not think about typesetting or macros or
> line endings.
>
Still in this area of annotations and rich documenting, I found another =
 =

more or less standard which could be of interest :
http://en.wikipedia.org/wiki/Epydoc
http://epydoc.sourceforge.net/
http://epydoc.sourceforge.net/manual-fields.html

Wikipedia says
> Epydoc is a documentation generator that processes its own lightweight=

> markup language Epytext for Python documentation strings. As opposed t=
o
> freeform Python docstrings, reStructured Text (both also supported) an=
d
> other markup languages for docstrings, Epytext supports linking betwee=
n
> different pieces of documentation.
What I particularly enjoy here, is the part =E2=80=9Csupports linking be=
tween  =

different pieces of documentation=E2=80=9D.

While there are multiple standards covering similar things (I would like=
  =

one single standard, not many), there is at least one aspect which seems=
  =

there all the time : the meaning of =E2=80=9C@=E2=80=9D as introducing a=
nnotations. You  =

got it in Java, C, Python, FunnelWeb, among others. That's widely used  =

enough. At least a step to something standard=E2=80=A6 (I still miss man=
y and many  =

things).

-- =

Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es=
t pas pour  =

les chiens.

=E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]