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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,794a4cb8f6cfe39b X-Google-Attributes: gid103376,public From: geert@fozzie.sun3.iaf.nl (Geert Bosch) Subject: Re: Clear Screen Date: 1997/02/26 Message-ID: <5f15dg$an@fozzie.sun3.iaf.nl>#1/1 X-Deja-AN: 221559326 References: <330FE569.29FA@bix.com> <5erk3a$a29@news.cict.fr> Organization: La Calandre Infortunee Newsgroups: comp.lang.ada Date: 1997-02-26T00:00:00+00:00 List-Id: Robert Dewar (dewar@merv.cs.nyu.edu) wrote: "This is the second person to write Character'Val(27) rather than the much clearer Ascii.ESC! " Maybe you could explain why the perfectly reasonable and standard use of Ascii.ESC, Ascii.TAB etc has been declared obsolete? Using Latin_1 requires withing Ada.Characters.Latin_1 and using or renaming it or its parent in every module that wants to use one of the standard and well-known Ascii values. This makes it harder/more work to use the constants, so novice users (the majority) will be unlikely to use Latin_1 when they just need that @$#%^& value for a horizontal tab, linefeed or escape. In many cases it is better to use the Standard.Ascii package than the Ada.Characters.Latin_1 package anyway. When I want to use ANSI escape sequences like the clear screen in the example, I just want to use the named ASCII characters, since I cannot assume the terminal uses the Latin-1 character set. Also when I write Ascii.LF everybody knows what I mean, but when I write Ada.Characters.Latin_1.LF it might not be clear I'm just using the Ascii linefeed character. IMHO using Latin_1 on a system that doesn't support Latin_1 makes no sense. Regards, Geert -- -- E-Mail: geert@sun3.iaf.nl -- `` If trainstations are places where trains stop, -- then what are workstations? ''