[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev lynx2.8.4dev.17

From: pg
Subject: Re: lynx-dev lynx2.8.4dev.17
Date: Sat, 10 Feb 2001 18:52:54 -0700 (MST)

In a recent note, Thomas Dickey said:

> Date: Sat, 10 Feb 2001 20:22:32 -0500
> some platforms have unsetenv(), which my Linux manpage says is BSD 4.3
> (however, not everyone has it - you may end up making your own to
> remove an entry from 'environ', or simply rename a variable temporarily,
> e.g., "LINES" to "_LYNX" and "COLS" to "LYNX" - ugly but easy).
Ugly indeed.  I suspect I must then unrename it before I do another
putenv() with the same name, else I create a memory leak.

Even uglier, OS/390's putenv() makes a copy of its argument string to
put in the environment.  I suspect this is a POSIX violation; I need
to research and start an issue with IBM if so.  So far, IBM employees
(and customers) have told me unofficially that IBM is only doing me
a favor by allowing me to safely use automatic variables as arguments
to putenv() -- they boast of it in TFM.


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]