From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,INVALID_DATE, MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!icdoc!umace03 From: umace03@doc.ic.ac.uk (M Y Ben Gershon) Newsgroups: comp.lang.ada Subject: Re: Enumeration_IO Message-ID: <1874@gould.doc.ic.ac.uk> Date: 9 May 90 22:36:51 GMT References: <1846@sparko.gwu.edu> <1117@software.software.org> <1850@sparko.gwu.edu> Sender: news@doc.ic.ac.uk Reply-To: umace03@doc.ic.ac.uk (M Y Ben Gershon) Organization: Imperial College Department of Computing List-Id: >In article <1850@sparko.gwu.edu> mfeldman@seas.gwu.edu (Mike Feldman) writes: > Change > > COLOR_IO.PUT(ITEM => C, SET => LOWER_CASE); > to > COLOR_IO.PUT(ITEM => C, SET => TEXT_IO.LOWER_CASE); > ^^^^^^^^ Yes, OK. But why doesn't COLOR_IO.LOWER_CASE work, seeing that we are using package COLOR_IO is new TEXT_IO.ENUMERATION_IO(ENUM => COLORS); shouldn't it follow that LOWER_CASE is distinct for each separate instantiation of TEXT_IO. ? Yet, if I put COLOR_IO.LOWER_CASE it doesn't work, giving the same error message as before. Michael Ben-Gershon umace03@doc.ic.ac.uk