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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC 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: David Shochat Subject: Re: Environment variables Date: 1996/11/01 Message-ID: <327A32A3.2DD0@itg-sepg.logicon.com>#1/1 X-Deja-AN: 193760366 references: <55819q$mql@newslink.runet.edu> content-type: text/plain; charset=us-ascii organization: Logicon Information Technology Group mime-version: 1.0 reply-to: shochat@itg-sepg.logicon.com newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (Win95; U) Date: 1996-11-01T00:00:00+00:00 List-Id: 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. When a C programmer wants to read environment variables, she doesn't have to choose among 6 different interfaces and worry about what happens when she moves the code to a different vendor's compiler etc. I know reading environment variables is an extremely exercise in pragma Import, but this sort of thing should just be there to use. As it is for the C programmer (regardless of whose compiler he is using). ..Sigh -- David