From: "David C. Hoos, Sr." <david.c.hoos.sr@ada95.com>
Subject: Re: Setting Environment Variables
Date: 2000/05/12
Date: 2000-05-12T19:48:40+00:00 [thread overview]
Message-ID: <8fhn6o$3ke$1@hobbes2.crc.com> (raw)
In-Reply-To: 391C43C9.5F7DA9E3@Raytheon.com
Samuel T. Harris <samuel_t_harris@Raytheon.com> wrote in message
news:391C43C9.5F7DA9E3@Raytheon.com...
> David Emery wrote:
> >
> > This is specified in POSIX/Ada, since it's really an OS operation.
> >
> > dave
>
> So are command-line arguments but they are supported
> directly in Ada 95. I find this "its an OS operation"
> line of reasoning dubious. Ada.Command_Line specifies
> what happens when an implementation has no command-line,
> so why not have an Ada.Environment as well?!!!
>
Well, reading the existing environment could, of course, be
easily done. But... setting an environment variable often
requires enlarging the environment space -- meaning copying
the old stuff plus the modification, and deallocating the old, etc.
Some flavors of UNIX don't (or at least didn't 8 years ago) support
setenv, and I remember that VADS was seriously broken on at
least one platform, at that time with an Ada procedure for Setenv.
next prev parent reply other threads:[~2000-05-12 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-08 0:00 Setting Environment Variables John Lee
2000-05-08 0:00 ` Larry Kilgallen
2000-05-11 0:00 ` David Emery
2000-05-12 0:00 ` Samuel T. Harris
2000-05-12 0:00 ` David C. Hoos, Sr. [this message]
2000-05-08 0:00 ` Gisle S�lensminde
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox