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,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9c86eb13dd395066 X-Google-Attributes: gid103376,public From: jsa@alexandria (Jon S Anthony) Subject: Re: CRC in Ada? Date: 1997/03/17 Message-ID: #1/1 X-Deja-AN: 226253451 Distribution: world References: <1997Mar2.220652@nova.wright.edu> <1997Mar5.131846.1@eisner> Organization: PSI Public Usenet Link Newsgroups: comp.lang.ada Date: 1997-03-17T00:00:00+00:00 List-Id: In article dewar@merv.cs.nyu.edu (Robert Dewar) writes: > Jon said > > < be composed of elements whose type is user defined and which have > their own specialized 'Read and 'Write. There's no way to handle this > sort of thing in general except to just call the things element by > element.>. > > Well of course, but the compiler knows perfectly well when this is the case, Well, of course I agree with this - it's the reason I suggested the "as if" optimization in the first place. > On the other hand, this does not stand in the way at all from optimizaing > certain cases where the user has NOT specialized things this way. Absolutely. And that is why I suggested it. > Of course, as always, the existence of the general case tends to mean that > the optimized case gets put aside (consider the influence on Fortran > compilers of the fact that format strings *may* be dynamic -- for a long > time the result was that Fortran runtimes treated all format strings as Agreed. Picking certain "strategic" special cases to optimize can work near miracles in practice! /Jon -- Jon Anthony Organon Motives, Inc. Belmont, MA 02178 617.484.3383 jsa@organon.com