Re: an interested business-oriented programmer

["Marin David Condic" <marin.condic.auntie.spam@pacemicro.com>]

Thanks for the clarification. If I understand correctly, you are saying the
normative annexes have to pass validation *if* an implementation claims to
support them.

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/

"Stanley R. Allen" <u384k@gsde.hou.us.ray.com> wrote in message
news:3B1F9173.C7D51A74@gsde.hou.us.ray.com...
> "Normative" in this context means that it provides a norm
> (standard) -- it does not mean that the validation of a
> compiler is dependent on implementing the annex.  It means
> that if a compiler creator DOES provide Annex F, that the
> validation of that annex must meet the standard's definition
> in order for Annex F to be so noted in the validation.
>
> Other annexes (K, L, & M for example) are "informative" --
> they don't provide extra 'normative' requirements beyond what
> was given elsewhere in the standard.
>