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,MAILING_LIST_MULTI, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6bf481efd29cf77b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-12 07:20:20 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!fr.clara.net!heighliner.fr.clara.net!freenix!enst!enst.fr!not-for-mail From: "David C. Hoos" Newsgroups: comp.lang.ada Subject: Re: Behavior of Stream Attributes On Access Types. Date: Wed, 12 Jun 2002 09:19:54 -0500 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: References: <4519e058.0206110547.526d2369@posting.google.com> Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 1023891619 56612 137.194.161.2 (12 Jun 2002 14:20:19 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Wed, 12 Jun 2002 14:20:19 +0000 (UTC) Return-Path: X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: comp.lang.ada mail<->news gateway List-Unsubscribe: , Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: archiver1.google.com comp.lang.ada:25795 Date: 2002-06-12T09:19:54-05:00 ----- Original Message ----- From: "Marin David Condic ]" Newsgroups: comp.lang.ada To: Sent: Tuesday, June 11, 2002 9:37 AM Subject: Re: Behavior of Stream Attributes On Access Types. > Just to make sure I'm getting this correct in my brain, try this one out for > me: I have a tagged record that does not have any access values in it, so > using the standard-issue 'Output and 'Input is just fine. I inherit from > this and add some access values, so I need to create my own 'Read and > 'Write, correct? (But not 'Output and 'Input) Then, 'Output and 'Input for > that descendent should work correctly without overriding anything, right? > Further, using the base type's 'Class'Output and 'Class'Input should work > correctly by dispatching up the ladder to find my home-grown 'Read and > 'Write, correct? Then, just to make it more interesting, I inherit from the > second type and add more (non-access) fields. I *must* override my own 'Read > and 'Write to include the newly added fields? Or will it dispatch to the > 'Read and 'Write in the second level, then go on to call the defaults for > the newly added fields? > You only need to add read and write for the _access_ types. 'Output and 'Input are never overridden, as they always use 'Read and 'Write. The only other cases for which I have had to override the standard stream attributes is when there are machine endianess issues in network representation of data. Did you look at my example of how I do it?