Re: Overriding 'Class'Input (was: List container strawman 1.1)

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

O.K. But this post kind of implies that there is a reason you would want to
implement S'Input instead of S'Read - saying that S'Class'Input is going to
find its way to the S'Input you implement for the specific type. This
degenerates to the S'Read because the compiler will be smart enough to
figure out it should write bounds/discriminants/tags, then call your
replacement for S'Read?

If that's the case, it makes it a lot simpler than I previously had thought.
It also seems to explain where the 'Read and 'Write are useful since after
initially looking at them, I didn't know why I'd want them if they didn't
write out the tags, etc. (The 'Input and 'Output seem to be what you
normally want to use - getting them automagically by defining 'Read and
'Write makes more sense.)

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Ted Dennison" <dennison@telepath.com> wrote in message
news:ACaN7.41163$xS6.69385@www.newsranger.com...
> In article <9paN7.41146$xS6.69394@www.newsranger.com>, Ted Dennison
says...
>
> In the interest of interjecting a rare bit of fact into one of my
discussions, I
> went back to Deja to look this up. The best I could find was a thread from
'99
> where Matthew Heaney (*not* Tucker) told me that 'Class'Input comes from
'Input,
> and *implied* that it isn't really useful to override 'Class'Input. That's
not
> particularly helpful to your specific issue though.
>
> You can read the post yourself at
>
http://groups.google.com/groups?q=%27Class%27Input+group:comp.lang.ada&hl=xx
-bork&rnum=1&selm=3803cc6c_1%40news1.prserv.net
>