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-Thread: a07f3367d7,9983e856ed268154
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.66.74.102 with SMTP id s6mr1419239pav.21.1345326748574;
        Sat, 18 Aug 2012 14:52:28 -0700 (PDT)
Received: by 10.180.103.197 with SMTP id fy5mr1176981wib.1.1345326748180;
        Sat, 18 Aug 2012 14:52:28 -0700 (PDT)
Path: 
 kg8ni1532pbc.0!nntp.google.com!news1.google.com!7no23450904wig.0!news-out.google.com!n2ni198820048win.0!nntp.google.com!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Should Inline be private in the private part of a package spec?
Date: Sat, 18 Aug 2012 22:52:27 +0100
Organization: A noiseless patient Spider
Message-ID: <m2boi7yijo.fsf@nidhoggr.home>
References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net>
	<1mchat48i3fos.1ksbz02nuzf5f$.dlg@40tude.net>
	<k0ei0u$214$1@munin.nbi.dk>
	<rznvpohy5adk$.1of2k7nklsaam.dlg@40tude.net>
	<502b832f$0$6579$9b4e6d93@newsspool3.arcor-online.net>
	<vqx5pu5yd4m7.jlystys02zcx$.dlg@40tude.net>
	<502bc4df$0$6574$9b4e6d93@newsspool3.arcor-online.net>
	<sgy28ka2rw0a.119txios2lu0g$.dlg@40tude.net>
	<502bd3e6$0$6574$9b4e6d93@newsspool3.arcor-online.net>
	<17qgsq5y7or0v.16z18fmcew1lt$.dlg@40tude.net>
	<502c149e$0$6579$9b4e6d93@newsspool3.arcor-online.net>
	<ak8h9w7770bx$.ncrikznng6v3$.dlg@40tude.net>
	<502cd701$0$6568$9b4e6d93@newsspool3.arcor-online.net>
	<pstv4iafyysv$.1mq6dicsj9my0.dlg@40tude.net>
	<502d3c68$0$6572$9b4e6d93@newsspool3.arcor-online.net>
	<mhbnq53dwqt2.r7w4k1ptmxf1$.dlg@40tude.net>
	<502e9039$0$6557$9b4e6d93@newsspool4.arcor-online.net>
	<40tmogy4d1b5.1kc2gm8qfrkdu.dlg@40tude.net>
	<op.wi78rmfska8ora@aspire.local>
	<17eab721-33da-4957-ab73-63221f1a9f6f@googlegroups.com>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="f0da64ccd4791c80ba5fb6b10d855629";
	logging-data="23447"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/iolRzBgbjDC3OHXwzBcVSyU0VnEcMPNM="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (darwin)
Cancel-Lock: sha1:KyUq5/2U0i5Drepk4pi0h/cAkI0=
	sha1:O5jHUQFbrH55uyzO1xP5DDeDOdQ=
Content-Type: text/plain
Date: 2012-08-18T22:52:27+01:00
List-Id: <comp.lang.ada>

Shark8 <onewingedshark@gmail.com> writes:

> Neither. PostScript is a fully functional programming language, albeit
> specialized for display/printing.
>
> In fact, I believe it to be a better solution than HTML/CSS for
> layout-specification. (Remember, HTML was *designed* to allow
> renderers to choose their own layout, virtually all CSS's layout
> attributes are due to this design decision... and, indeed, produces a
> practical illustration of what happens when the wrong tools are
> selected for a particular job [i.e. web-designers trying to get their
> pages to display the same across platforms are working against a
> design-decision of HTML].)

So you propose we should write blogs etc in PostScript?!!!! Count me
out.