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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!newsfeed.fsmpi.rwth-aachen.de!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 19 Feb 2014 16:37:42 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Text_IO, was: Re: Something I don't understand References: <4a3e55f6-9f54-4084-9f37-96efd4b0d349@googlegroups.com> <0b358700-871b-4603-addd-65e07c7d59e5@googlegroups.com> <13cmx8lollig2.1ic40x57wows8$.dlg@40tude.net> <1mh0lp04e4bzc.vr6hi3fcbba5.dlg@40tude.net> <7gb1iv15zuh$.1qbeifwuyvuoa.dlg@40tude.net> In-Reply-To: <7gb1iv15zuh$.1qbeifwuyvuoa.dlg@40tude.net> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-ID: <5304cfc5$0$9515$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 19 Feb 2014 16:37:41 CET NNTP-Posting-Host: 9b403b43.newsspool1.arcor-online.net X-Trace: DXC=lBTNRIT0_ZL74okIm;?DS@ic==]BZ:afN4Fo<]lROoRAnkgeX?EC@@@?Z7BlCkWK7Gnc\616M64>JLh>_cHTX3jMKJ0JINC37TB X-Complaints-To: usenet-abuse@arcor.de Xref: news.eternal-september.org comp.lang.ada:18669 Date: 2014-02-19T16:37:41+01:00 List-Id: On 19.02.14 15:13, Dmitry A. Kazakov wrote: > Compared to direct dispatch to the implementation tailored for the give > medium. Why do I need HTML in order to write a stream or memory string? The normal use case for HTML is when there are at least two computer systems involved: (1) one sending documents (->), and receiving requests (<-), ███████████████████████████ ███████████████████████████ (2) one receiving documents (<-), and sending requests (->), such that each of them is controlled exclusively by different parties. There is no dispatching, because a common dispatcher is an impossible part of the setup. (IOW, the possibility is only a mathematical one, whenever it refuses to include earthly constraints of the setup.) The media types of CSS will allow an HTML processor to render the same HTML on a number of different devices. Still, no MD. However, once the equivalence class of XSL is taken into account, you get MD, at least conceptually. But it happens outside the "producer" program (1).