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,8dea6f46dfb95f66 X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Environment variables Date: 1996/11/02 Message-ID: <1996Nov2.173625.1@eisner>#1/1 X-Deja-AN: 194099511 x-nntp-posting-host: eisner.decus.org references: <55819q$mql@newslink.runet.edu> <327A32A3.2DD0@itg-sepg.logicon.com> x-nntp-posting-user: KILGALLEN x-trace: 846974227/2310 organization: LJK Software newsgroups: comp.lang.ada Date: 1996-11-02T00:00:00+00:00 List-Id: In article <327A32A3.2DD0@itg-sepg.logicon.com>, David Shochat writes: > This whole thread is making me rather sick. I was recently involved with > an effort involving porting a good bit of Ada 83 code to Ada 95, in > which the necessary conversion of X-windows code from "AXI Bindings" to > "Intermetrics Bindings" was fairly massive and non-trivial. > > My point is that things like reading environment variables should be > standardized. On our project we have tried to stick to the POSIX > packages (Forest for us -- the newer one wasn't available when we > started) for Unix interface functions which aren't standardized in the > RM. Although some may be able to limit use of their projects to running in a Posix environment, not every project can live with that constraint. Aside from Unix systems, most Posix environments are separate environments from the native environment for a platform, and often there are requirements to use X-windows outside the Posix environment. The particular example of "environment variables" does not make sense outside Posix/Unix, so those who have been bitten once by a portability issue should consider future porting requirements as well. Larry Kilgallen