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,bb3c718a1fb5b85c X-Google-Attributes: gid103376,public From: Matt O'Hara Subject: Re: GNAT for NT Linking Problem Date: 1996/09/25 Message-ID: <32499EE7.39D0@lmco.com>#1/1 X-Deja-AN: 185327393 references: <32342D50.1E1C@planet8.eag.unisysgsg.com> <3234724E.251E@joy.ericsson.se> <5124sl$kjl@felix.seas.gwu.edu> <3246AB3C.4A17@ubs.com> content-type: text/plain; charset=us-ascii organization: Lockheed Martin - Tactical Defense Systems, Eagan, MN mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.02 (X11; U; HP-UX A.09.05 9000/712) Date: 1996-09-25T00:00:00+00:00 List-Id: > > Michael Feldman wrote: > Michael - Sorry; I started this topic and then got pulled away from it. > > Since you are porting to GNAT, why not take the opportunity to > > Ada 95-ize your program and get away from using those C libraries. > > For example, toupper, etc., are part of the Ada 95 standard libs, > > in this case Ada.Characters.Handling. > > I have started to do this, although I have discovered a limitation with Ada95 that I did not care for. See the next response... > > And why use the C IO routines? Is there a problem with Ada.Text_IO? > > > > The only thing I can think of that would require the C libs is if > > (possibly) those f* routines are unbuffered. Do you need unbuffered > > input/output? > > We used the C IO routines because Ada 83 Text IO (which the original code was based on) could not handle Japanese (Wide) characters, and we needed to Internationalize our program. Since we were Solaris based, and Solaris has all these nice, neat Wide libraries, we simply built our own text_io replacement package which used our own wide_character types, and interfaced to the Solaris C wide libraries. Ada 95 does have wide_character functions, including I/O. Although I am still playing around with converting this to Ada95, I have noticed that its Wide_Io does not handle wide_character file/path names; they are String only. This seems like an unnecessary restriction; the wide_io package we developed allowed wide_character file names. Why should Ada 95 force non-English developers to use only English names? > > Mike Feldman > > -- Matthew H. O'Hara Principal S/W Engineer Lockheed Martin Tactical Defense Systems, Eagan, MN 612-456-3228 matthew.h.ohara@lmco.com