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.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,577c9f9c0cdd76d X-Google-Attributes: gid103376,public From: Nick Roberts Subject: Re: Confusing language, was Re: Help help.. please.i am totaly new in ada programing Date: 1999/11/13 Message-ID: <382DAF3F.D69B74A4@callnetuk.com>#1/1 X-Deja-AN: 548214874 Content-Transfer-Encoding: 7bit References: <7vqgs2$lcc$1@nnrp1.deja.com> <38233108.F3540F0@ebox.tninet.se> <806716$i6c2@ftp.kvaerner.com> <807109$8m0$1@nnrp1.deja.com> <38270DC7.86553BB1@pwfl.com> <38285C60.B3E2D2BC@pwfl.com> <809u91$3ik$1@nntp1.atl.mindspring.net> <80djd2$48o$1@nnrp1.deja.com> <382C40FA.248E6840@mitre.org> <80ival$og$1@nnrp1.deja.com> X-Original-NNTP-Posting-Host: da132d209.dialup.callnetuk.com X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Trace: 13 Nov 1999 19:42:17 GMT, da132d209.dialup.callnetuk.com Organization: Computer Consultant MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-11-13T00:00:00+00:00 List-Id: Robert Dewar wrote: > In article <382C40FA.248E6840@mitre.org>, > "Robert I. Eachus" wrote: > > Streams should value portability over speed > > I strongly disagree in two contexts: > ... > 2. For homogenous distributed applications, the efficiency > of streams is critical in the performance of remote procedure > calls. Aaaargh! Inefficient streams would *seriously knacker* a system based heavily on Annex-E based IPC. (Guess who is in the process of designing such a system ;-) Apologies if I'm repeating somebody, but RM95 13.13.2 (17) has the following implementation advice: : If a stream element is the same size as a storage element, then the : normal in-memory representation should be used by Read and Write for : scalar objects. Otherwise, Read and Write should use the smallest : number of stream elements needed to represent all values in the base : range of the scalar type. > > Or maybe we need multiple predefined stream types with > > different characteristics. > > That's a much better thought in my opinion. > We need a way of specifying default stream methods Much better idea. Maybe a new configuration pragma could be used for this job? pragma Default_Stream_IO ( Intrinsic | Standard ); Intrinsic would invoke the current recommended scheme (efficient in-memory images), and so be the default. Standard would invoke a scheme which precisely specified the binary format of every possible Ada type (for all four attributes Read, Write, Input, and Output). I think this would have to be in terms of architectures which had byte (or byte-multiple) stream elements and elementary types; architectures which didn't would simply have to ignore the pragma or interpret it in their own way (but issue a warning!). Submission for an AI? -- Nick Roberts Computer Consultant (UK) http://www.callnetuk.com/home/nickroberts http://www.adapower.com/lab/adaos