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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC 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,ASCII-7-bit Received: by 10.204.129.81 with SMTP id n17mr129922bks.3.1345716802296; Thu, 23 Aug 2012 03:13:22 -0700 (PDT) Received: by 10.180.24.202 with SMTP id w10mr324631wif.0.1345716801856; Thu, 23 Aug 2012 03:13:21 -0700 (PDT) Path: m12ni126129bkm.0!nntp.google.com!news1.google.com!yt1no41326429wib.1!news-out.google.com!q11ni273595072wiw.1!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!195.238.0.231.MISMATCH!news.skynet.be!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Should Inline be private in the private part of a package spec? Date: Thu, 23 Aug 2012 12:13:36 +0200 Organization: cbb software GmbH Message-ID: <1i9sfhbz3harl$.1ihaky0f5ne8d$.dlg@40tude.net> References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net> <50326457$0$6576$9b4e6d93@newsspool3.arcor-online.net> <1qril0ny3eczr$.1vlhpbrjyyb8k.dlg@40tude.net> <503375ac$0$6565$9b4e6d93@newsspool3.arcor-online.net> <1vglgit7vnu4l$.2ytljabrhk2.dlg@40tude.net> <5033986c$0$6573$9b4e6d93@newsspool3.arcor-online.net> <62h5nifarvom.1myeqdyevhefq.dlg@40tude.net> <5033b4d8$0$6571$9b4e6d93@newsspool3.arcor-online.net> <5033ff28$0$6185$ba4acef3@reader.news.orange.fr> <5034dac1$0$6579$9b4e6d93@newsspool3.arcor-online.net> <50350d35$0$6579$9b4e6d93@newsspool3.arcor-online.net> <1xdzh15anpuc0.1xw8mwmojasjk$.dlg@40tude.net> <50354c95$0$6577$9b4e6d93@newsspool3.arcor-online.net> <1sfidfvz480e7$.l49woc2l4lji.dlg@40tude.net> <5035f059$0$6580$9b4e6d93@newsspool3.arcor-online.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: FbOMkhMtVLVmu7IwBnt1tw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: 2012-08-23T12:13:36+02:00 List-Id: On Thu, 23 Aug 2012 10:56:57 +0200, Georg Bauhaus wrote: > On 23.08.12 09:23, Dmitry A. Kazakov wrote: > >> and XML stands in their way. > > If XML stands in your way, OK. Here is the exchange you cut: > On Wed, 22 Aug 2012 23:18:16 +0200, Georg Bauhaus wrote: >> On 22.08.12 19:44, Dmitry A. Kazakov wrote: >>> On Wed, 22 Aug 2012 18:48:03 +0200, Georg Bauhaus wrote: >>>> On 22.08.12 16:30, Dmitry A. Kazakov wrote: >>>>>> As always, the question is inefficient for what and for whom. >>>>> For the network and the peers. The measures for both can be easily >>>>> provided. >>>> Well, that would depend on the specifics of "network" and its mode >>>> of use, wouldn't it? >>> There exist pretty general measures, e.g. number of bits, FLOPs, QoS and so >>> on. >> In the set called "and so on", information retrieval programs will >> be efficient at all once they can interpret a data item to be an object >> for which FLOPs make any sense. > and XML stands in their way. >>> That's easier to see when there is >>> markup than when the program needs to guess > >> Wasting time and memory. > > So laborious guessing, looking for clues, is cheaper than just looking > at a tag that clearly identifies the intent of the tagged item? Nobody needs either parsing or guessing in order to exchange structured data. Things you describe maybe are consequences of deployment of XML, but they are in no way the premises. > Remember: in my networks I work more like an archaeologist trying > to understand the shards. There are many thing one could do wrong. Using XML was seemingly not the only one. If you and others would not deploy XML in your networks, the "ceramic" would have been intact. >>>> Ada is not proposed for exchanging structured data >>>> between computers. >>> >>> It is, however, required to say how to exchange structured program >>> source text between compilers. >> >> No > > Yes, it is. Character set support, documentation requirements, ... see RM 2.1 regarding Ada character set and for the rest. The purpose of the language is described in RM 1. Otherwise, I repeat: Ada is not proposed for exchanging structured data. Thus any references to Ada are irrelevant. >>>> between computers. >>>> Ada is a programming language. XML in this context plays >>>> the role of a protocol to exchange above mentioned data. >>> >>> No. It is a markup language for tagging data in text documents. >>> We have been here before. >> >> That is it! XML is not for exchange of structured data. > > No, XML is not a protocol for whatsoever. Either "Yes, XML is not a protocol for whatsoever." or "No, XML is a protocol for exchange of structured data." -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de