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-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!de-l.enfer-du-nord.net!news.weisnix.org!newsfeed.ision.net!newsfeed2.easynews.net!ision!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Wed, 03 Jun 2009 21:43:05 +0200
From: Georg Bauhaus <rm.tsoh.plus-bug.bauhaus@maps.futureapps.de>
Reply-To: rm.tsoh+bauhaus@maps.futureapps.de
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Howto read line from a stream
References: 
 <83317a97-dae5-4c84-a1ac-88a87833cf3f@q14g2000vbn.googlegroups.com>
  <1a90e055-44a3-4d00-b4cd-64798c731a55@e24g2000vbe.googlegroups.com>
 <dXEUl.125959$DP1.74148@attbi_s22>
 <709e8a12-f967-43db-b76b-4852cf1db08b@v4g2000vba.googlegroups.com>
 <a86bd17a-8488-4d40-8aed-5bea60b89e67@e24g2000vbe.googlegroups.com>
 <196d124vj6gin.16zf5y40t9tr$.dlg@40tude.net>
In-Reply-To: <196d124vj6gin.16zf5y40t9tr$.dlg@40tude.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <4a26d249$0$31865$9b4e6d93@newsspool3.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 03 Jun 2009 21:43:05 CEST
NNTP-Posting-Host: 8a0d022c.newsspool3.arcor-online.net
X-Trace: 
 DXC=QTN^kgU`FLG@Y=h<_c3PkHMcF=Q^Z^V3H4Fo<]lROoRA^YC2XCjHcbIJE\0ln_FPEI;9OJDO8_SKFNSZ1n^B98iJDahKg8SGWjD
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:6193
Date: 2009-06-03T21:43:05+02:00
List-Id: <comp.lang.ada>

Dmitry A. Kazakov wrote:
> On Wed, 3 Jun 2009 12:07:16 -0700 (PDT), sjw wrote:
> 
>> But if you are dealing with character i/o I hardly think it matters!
>> Jeffrey's solution may take quite a bit of stack, if that's an issue.
> 
> You terribly underestimate the huge "progress" of idiotic protocols,
> beginning with XML.

Let's say, idiotic uses of XML. If the job is downloading
ready made configuration data to some hardware device, then
I'd find building an XML parser into the device as questionable
as doing the same for some Ada-like syntax. JSON is only slightly
better.

But FWIW, validated XML is easily and realiably transformed
into a packed, hardware-friendly, lossles, valid, efficient
configuration stream, tailored to the hardware's needs.

XML is for MOM.  Let there be middleware.