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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!necntc!adelie!mirror!ishmael!ada-uts!stt From: stt@ada-uts Newsgroups: comp.lang.ada Subject: Re: Characters with codes >= 128 Message-ID: <57900043@ada-uts> Date: Wed, 2-Sep-87 10:24:00 EDT Article-I.D.: ada-uts.57900043 Posted: Wed Sep 2 10:24:00 1987 Date-Received: Sun, 6-Sep-87 20:50:18 EDT References: <2231@enea.UUCP> Nf-ID: #R:enea.UUCP:-223100:ada-uts:57900043:000:1314 Nf-From: ada-uts!stt Sep 2 10:24:00 1987 List-Id: You may define your own enumeration type, but you are correct that only "standard" ASCII graphic characters may be used in character and string literals. For "characters" which have no standard ASCII graphic representation, you should define normal non-character enumeration literals. You may then define your own IO package (there is generally nothing "magical" about TEXT_IO, except that the compiler-writer has to provide it) to provide I/O for characters and arrays of these extended characters. Extended "string" literals can be created via concatenate of strings containing only graphic characters and enumeration literals for extended characters. S. Tucker Taft Intermetrics, Inc. Cambridge, MA 02138 P.S.: Here is an example: package Extended_ASCII is type X_Character is (NUL, SOH, . . ., 'a', 'b', . . ., UMLAUT, ALPHA, OMEGA, . . .); type X_String is array(Positive range <>) of X_Character; pragma Pack(X_String); end Extended_ASCII; with Extended_ASCII; use Extended_ASCII; package X_Text_IO is . . . procedure Put_Line(Str : X_String); . . . end X_Text_IO; with Extended_ASCII; use Extended_ASCII; with X_Text_IO; procedure Test is S : constant X_String := "This is an " & ALPHA & " to " & OMEGA & " test." begin X_Text_IO.Put_Line(S); end Test;