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
X-Google-Thread: a07f3367d7,9983e856ed268154
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,UTF8
Received: by 10.204.10.88 with SMTP id o24mr1802999bko.0.1345594505631;
        Tue, 21 Aug 2012 17:15:05 -0700 (PDT)
Received: by 10.180.82.226 with SMTP id l2mr56548wiy.1.1345594504347;
        Tue, 21 Aug 2012 17:15:04 -0700 (PDT)
Path: 
 m12ni123191bkm.0!nntp.google.com!news1.google.com!yt1no37190013wib.1!news-out.google.com!q11ni249853972wiw.1!nntp.google.com!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: "Vasiliy Molostov" <molostoff@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Should Inline be private in the private part of a package spec?
Date: Wed, 22 Aug 2012 04:15:02 +0400
Organization: None
Message-ID: <op.wje1nc1hka8ora@aspire.local>
References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net>
 <e416cb92-6ec8-4514-8fa9-c35d6432b117@googlegroups.com>
 <wcc4noj4zof.fsf@shell01.TheWorld.com> <jvnchp$r5c$1@munin.nbi.dk>
 <wccr4rkqed5.fsf@shell01.TheWorld.com> <op.wiml9rw3ka8ora@aspire.local>
 <502005b6$0$9510$9b4e6d93@newsspool1.arcor-online.net>
 <op.wim0pbprka8ora@aspire.local>
 <50203ca2$0$9512$9b4e6d93@newsspool1.arcor-online.net>
 <502040c0$0$9510$9b4e6d93@newsspool1.arcor-online.net>
 <k01amo$jio$1@munin.nbi.dk>
 <50677fa2-7f82-4ccc-8c56-161bf67fefe1@googlegroups.com>
 <k04a26$doi$1@munin.nbi.dk> <op.wius1gdbka8ora@aspire.local>
 <k0bubm$loe$1@munin.nbi.dk> <op.wi0fliuoka8ora@aspire.local>
 <k0eine$2h8$1@munin.nbi.dk> <op.wi113hf6ka8ora@aspire.local>
 <k1127v$roe$1@munin.nbi.dk>
NNTP-Posting-Host: Xw13RWgh8yxgPSv0x3+H9w.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/12.01 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
Date: 2012-08-22T04:15:02+04:00
List-Id: <comp.lang.ada>

Randy Brukardt <randy@rrsoftware.com> =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=
=B0) =D0=B2 =D1=81=D0=B2=D0=BE=D1=91=D0=BC =D0=BF=D0=B8=D1=81=D1=8C=D0=BC=
=D0=B5 Wed, 22 Aug  =

2012 02:31:22 +0400:

>
> "Vasiliy Molostov" <molostoff@gmail.com> wrote in message
> news:op.wi113hf6ka8ora@aspire.local...
> Randy Brukardt <randy@rrsoftware.com> ?????(?) ? ????? ?????? Wed, 15 =
Aug
> 2012 02:16:10 +0400:

> Maybe, but it all sounds like a fantasy to me. (Much about XML sounds =
 =

> like
> pure fantasy to me.)

Yep, like tasking in '80-90. It was a pure fantasy. But useful.

> Maintaining two ways to do the same thing is the ultimate in headaches=
 --
> you get to fix all bugs twice. For files not intended for use beyond t=
he
> compilation system, it doesn't make much sense to maintain more than o=
ne
> version. (We don't attempt to keep any sort of compatibility on these =
 =

> files
> now between different compiler versions.)

No, as I see it that new thing can be on top of already existing one, an=
d  =

this looks like an extension only, a king of.

> One could imagine having tools to extract information from the project=
  =

> files
> in some other format, but I doubt that we'd change the format a lot. (=
And
> such tools would require customer demand, obviously.)

This is one of the ways to attract more customers and minimize effort fo=
r  =

existing ones.
A file can be just another one, does not matter.