Re: Beware: Rep spec on an enumeration type causes code explosion

["John G. Volan" <johnv@ac3i.dseg.ti.com>]

Ken Garlington wrote:

> A response to this statement was: "There is no need for anything so
> elaborate." The corresponding code did the conversion without a
> check, which prompted me to ask how validity was handled.

Sorry, let me clarify: I wasn't commenting on the need to use 'Valid, of
course that is quite necessary. What I was getting at was that you
seemed to imply that the "holey" type ought to be something other than
an enumeration type, let's say an integer type; and that the programmer
should write some elaborate function involving perhaps a case statement
to do a mapping between valid integer values and the target enumeration
type.  All I was trying to show was that Ada's built-in type conversion
facility can "automagically" supply this mapping, if you simply derive a
"holey" enumeration type from a parent "contiguous" enumeration type.

-- 
------------------------------------------------------------------------
Internet.Usenet.Put_Signature 
  (Name       => "John G. Volan",
   Employer   => "Raytheon/TI Advanced C3I Systems, San Jose, CA",
   Work_Email => "jvolan@ti.com",
   Home_Email => "johnvolan@sprintmail.com",
   Slogan     => "Ada95: World's *FIRST* International-Standard OOPL",
   Disclaimer => "My employer never defined these opinions, so using " & 
                 "them would be totally erroneous...or is that just "  &
                 "nondeterministic behavior now? :-) ");
------------------------------------------------------------------------