Re: Behavior of Stream Attributes On Access Types.

["David C. Hoos" <david.c.hoos.sr@ada95.com>]

----- Original Message -----
From: "Marin David Condic ]" <dont.bother.mcondic.auntie.spam@[acm.org>
Newsgroups: comp.lang.ada
To: <comp.lang.ada@ada.eu.org>
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?