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,38159b1b5557a2e7 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-27 17:19:53 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!newsread1.news.pas.earthlink.net.POSTED!a6202946!not-for-mail From: Jeffrey Carter Organization: jrcarter commercial-at acm [period | full stop] org User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Standard Ada Preprocessor References: <400A9B48.3060100@noplace.com> <400BD4B5.6000307@noplace.com> <400BDB7C.40100@noplace.com> <400D2150.6000705@noplace.com> <400E72F9.8060501@noplace.com> <100upo7ln5e3k59@corp.supernews.com> <400FC8E8.2040100@noplace.com> <_JSdna166JuxFo3dRVn-hg@comcast.com> <401115B7.5020205@noplace.com> <101bjm54k3rn8f0@corp.supernews.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Wed, 28 Jan 2004 01:19:52 GMT NNTP-Posting-Host: 63.184.16.28 X-Complaints-To: abuse@earthlink.net X-Trace: newsread1.news.pas.earthlink.net 1075252792 63.184.16.28 (Tue, 27 Jan 2004 17:19:52 PST) NNTP-Posting-Date: Tue, 27 Jan 2004 17:19:52 PST Xref: archiver1.google.com comp.lang.ada:4964 Date: 2004-01-28T01:19:52+00:00 List-Id: Warren W. Gay VE3WWG wrote: > Some platforms for instance support asynchronous I/O. > Some with bugs, others not at all. If you are writing > servers, that BTW are very performance sensitive, then > if you can determine that asynch I/O works properly > (and well) on a given platform, then you're going to > use it! Anything less is inferior. > > For platforms where asynch I/O is defective or just > plain busted, you'll do things the plain old way you > always did it (with a corresponding hit in performance). If the performance on these latter systems is unacceptable, then you don't have a solution for those systems. If it is acceptable, then you have no portability problem, since you can use the plain old way on all systems and achieve acceptable performance. Either way you have no problem with or without a preprocessor. -- Jeff Carter "Son of a window-dresser." Monty Python & the Holy Grail 12