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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,be23df8e7e275d73
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-08-13 12:34:03 PST
Path: 
 archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!194.42.224.136!diablo.netcom.net.uk!netcom.net.uk!dispose.news.demon.net!news.demon.co.uk!demon!pogner.demon.co.uk!zap!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Proving Correctness (was Java Portability)
Date: 12 Aug 2001 07:34:43 +0100
Organization: CodeFella
Message-ID: <x7vvgjtn5vg.fsf@smaug.pushface.org>
References: <mailman.995648003.8404.comp.lang.ada@ada.eu.org>
 <9jrt62$38t$1@nh.pace.co.uk> <3B619A6D.5DD6E782@home.com>
 <DF897.3617$ee.3921026@nnrp5.proxad.net> <3B6636BA.96FD8348@home.com>
 <TLt97.9335$Xa.790630@nnrp4.proxad.net> <9kb3ub$hdo$1@a1-hrz.uni-duisburg.de>
 <yy9a7.3017$ss3.4363386@nnrp6.proxad.net>
 <9kchn1$lng$1@a1-hrz.uni-duisburg.de>
 <R1ta7.4077$ke.4769807@nnrp6.proxad.net> <9kea9a$lsc$1@nh.pace.co.uk>
 <9keduf$qvc$1@a1-hrz.uni-duisburg.de>
 <Reza7.18403$px7.4304991@nnrp1.proxad.net> <9kelv1$riq$
 <3B72CC18.F07195D1@ebox.tninet.se>
NNTP-Posting-Host: localhost
X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98
X-Trace: news.demon.co.uk 997731230 nnrp-10:20206 NO-IDENT
 pogner.demon.co.uk:158.152.70.98
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: 12 Aug 2001 06:34:43 GMT
X-Newsreader: Gnus v5.7/Emacs 20.7
Xref: archiver1.google.com comp.lang.ada:11865
Date: 2001-08-12T06:34:43+00:00
List-Id: <comp.lang.ada>

Stefan Skoglund <stetson@ebox.tninet.se> writes:

> I don't think an XML library would be that useful in an compiler
> targetting embedded applications.
> 
> Ow, nice we can send midcourse updates to the navigation
> computer as an XML stream. Really nice :-)

I don't quite see the problem here, I must say! after all, as an
example of using a high-level protocol in an embedded app, often
routers can be configured using an in-built http server.

My view is that if there is an (industry) standard {whatever} the
first approach considered should be to (re)use it.

Clearly this is less appropriate in the case where the unit cost
overwhelms the development effort.