Re: Newbie wanna Ada

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

I've never had an issue with a standard that said: "You are not required to
implement X but if you *do* implement X, it must meet these criteria..."

I would envision an Ada Standard Component Library as having some nice
"core" set of features that provided things that (almost) any implementation
could provide. Extensions could be added that covered different problem
domains not unlike the annexes in the ARM. A vendor could easily say
"Branches A, B and C compile nicely and work with my stuff so I'll accept
them but branches D and E I'm leaving out..." The important thing being that
*if* you need a certain set of features, you can count on the interface to
those features being consistent.

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:JzeC7.1464$xS6.2036@www.newsranger.com...
>
> There is the issue that not every Ada platform has TCP/IP. That's not an
> insurmountable problem, but it does mean that it would have to be in an
optional
> annex (Network Programming annex?)
>