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,ae40b60d59bcdc4b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-11 13:07:46 PST Path: supernews.google.com!sn-xit-03!supernews.com!newsfeed.wirehub.nl!newspeer1.nac.net!colt.net!newspeer.clara.net!news.clara.net!news5-gui.server.ntli.net!ntli.net!news2-win.server.ntlworld.com.POSTED!not-for-mail From: "chris.danx" Newsgroups: comp.lang.ada References: <3AD49CB1.9160D850@earthlink.net> Subject: Re: Ada Examples and Problems X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <0F2B6.4430$Ow3.938359@news2-win.server.ntlworld.com> Date: Wed, 11 Apr 2001 20:56:04 +0100 NNTP-Posting-Host: 62.253.13.32 X-Complaints-To: abuse@ntlworld.com X-Trace: news2-win.server.ntlworld.com 987018940 62.253.13.32 (Wed, 11 Apr 2001 20:55:40 BST) NNTP-Posting-Date: Wed, 11 Apr 2001 20:55:40 BST Organization: ntlworld News Service Xref: supernews.google.com comp.lang.ada:6784 Date: 2001-04-11T20:56:04+01:00 List-Id: > This just reminded me of a thread that was raging here for awhile last > year regarding the 'Size of types and objects versus the number of bytes > objects occupy in a stream (stream meaning the Stream_IO kind of > stream). > > Bottom line: There is _no_ required correspondence between those sizes. > > This can be frustrating at times, and did engender some smoke and fire > in the newsgroup. There are situations where one wants to know ahead of > time how many bytes something is going to occupy in a stream, but Ada > does not require that an ability to make that determination for all > types be available. Maybe this would be a good idea for addition in Ada 0y. An attribute that gives the total number of bytes/bits occupied by the fields not the record size. T'save_me_a_headache or T'field_bytes Bye, Chris