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: ChineseT,UTF8 Received: by 10.180.24.165 with SMTP id v5mr627175wif.1.1345237678711; Fri, 17 Aug 2012 14:07:58 -0700 (PDT) Path: n2ni181726861win.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.138.MISMATCH!xlned.com!feeder5.xlned.com!feed.xsnews.nl!border-1.ams.xsnews.nl!plix.pl!newsfeed2.plix.pl!217.153.128.51.MISMATCH!nf1.ipartners.pl!ipartners.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!gegeweb.org!aioe.org!.POSTED!not-for-mail From: "Vasiliy Molostov" Newsgroups: comp.lang.ada Subject: Re: Should Inline be private in the private part of a package spec? Date: Wed, 15 Aug 2012 07:02:05 +0400 Organization: None Message-ID: References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net> <502005b6$0$9510$9b4e6d93@newsspool1.arcor-online.net> <50203ca2$0$9512$9b4e6d93@newsspool1.arcor-online.net> <502040c0$0$9510$9b4e6d93@newsspool1.arcor-online.net> <50677fa2-7f82-4ccc-8c56-161bf67fefe1@googlegroups.com> <44bb5c96-a158-41c1-8e7d-ae83b2c0aca1@googlegroups.com> <1552e0d9-7cdf-4075-89d2-9a722c989c8e@googlegroups.com> <9c19af7c-b50a-499f-970f-45f0f6844226@googlegroups.com> 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-15T07:02:05+04:00 List-Id: Shark8 =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, 15 Aug 2012 = 04:50:14 +0400: > On Tuesday, August 14, 2012 5:59:47 PM UTC-6, Vasiliy Molostov wrote: >> Shark8 =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, 15 Aug = >> 2012 > Which are routinely subverted by those that break out regex as their = > "parser" of choice. Further it is a horrible format for random-access,= = > as Randy pointed out, requiring a read-through (parsing) for anything;= For a developer it is a matter of one index file to parse it only once, = if = this is a problem. > even if you know exactly *where* in your tree-structure it is. {By bei= ng = > in text-format you lose a *lot* of desirable properties.} Which ones? EOF delimiters? > This is what makes it unsuitable for many data-intensive applications.= All the web for today works on top of xml, btw. it is very data-intensiv= e. > I had the chance to work with Combat XXI a few years back --absolutely= = > HUGE Java-program; so much so that ANT couldn't auto-compile it in one= = > go and I needed to write a utility to generate sub-make instructions = > iterating over the subdirectory tree, leaves-to-root, to ensure that = > everything compile-- as I was talking to one of the other devs they = > mentioned that they had to write a binary-equivalent of XML for saving= = > the simulation... Perhaps you are a second man complaining about broken ant builder, one o= f = my friends also had similar problem indeed. Keeping such a binary for on= ly = one ant tool and loose all other constructive and profitable things is = possibly a short-sighted solution, where indeed it is an internal ant = problem. > because saving as text made the load too slow, and the text bloated th= e = > file-sizes to unacceptable levels. ...and depends on structure and content, at first. > So, even where I concede that XML may be useful (storing objects and = > their states) it has shortcomings. {Some parsers require keeping the X= ML = > structure in-memory; this creates a similar problem as Combat XXI's = > run-saving, but becomes a problem much earlier: most computers don't = > have a dozen GB to throw around at a problem.} xml is a stream oriented format, at first. Perhaps some not good = implementation should not revert an opinion on technology by itself. Badly programmed A= da = package can not express (invoke a claim) that Ada is bad itself for a whole. > Given the above [counter-]example, I believe that I have at least give= n = > enough evidence to cause one to rethink that statement. A compiler nee= ds = > a lot of information, true; but that doesn't mean that such informatio= n = > should be bloated by its transport-layer Transport? Why transport? Interchange layer. > -- that would be like applying multiple analog-to-digital and = > digital-to-analog conversions in audio systems: doing a lot of work fo= r = > nothing, that A-to-D step should happen only once, and [some of] the = > most hardcore audiophiles will invest in things on the analog side of = = > the switch, which is why you can find amplifiers using vacuum-tubes.) Interesting paragraph, but it does not relate to xml, xmi, uml or anothe= r = development tool. Perhaps you can get an example of use xml in ODT/ODF file format = (previously binary) developed by OASIS and widely used in MS/Libre world in packages like Openoffice, and= = even is a nation wide standard for now. I found it fast, accessible by handy tools like scripting, like access from an ada application using = xmlada or any other xml reader. Another good example is a docbook format widely used in publishing = industry. Even Dmitry A. Kazakov usually configures his hardware devices= = with xml based configurations (only imagine - xml parser in a device !!!= = :-O, lol how many things we can discover today ), to say more, at most a= ll = of ISP provider routers are controlled and configured over IGD protocol = = which is a subset of xml (indeed a wsdl). So perhaps a wind of changes = already has gone, much time ago. We have xml based world here (on a = development host). And surprisingly, a copy conversion from one format to another gives no = = degraded quality - check it with google docs. I think that a compilation result is not only a set of object files but = = also an automated report (standalone document) where all actions undertaken and dependencies resolved by the compiler are simply = = described, so a typical customer (or even a compiler itself) can dig it = = and find data from it useful for his own tool/purpose. The first and most useful thing here is an automated test generation, i = = suppose, and not a "project management". -- = =D0=9D=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE =D0=B2 =D0=BF=D0=BE=D1=87= =D1=82=D0=BE=D0=B2=D0=BE=D0=BC =D0=BA=D0=BB=D0=B8=D0=B5=D0=BD=D1=82=D0=B5= =D0=B1=D1=80=D0=B0=D1=83=D0=B7=D0=B5=D1=80=D0=B0 Opera: http://www.oper= a.com/mail/