setenv.c in recent 2.3 snapshot
rra at stanford.edu
Mon Dec 6 23:35:08 UTC 1999
Heath Kehoe <hakehoe at norand.com> writes:
> Hey, all...
> The lib/setenv.c file needs to include libinn.h and string.h to get
> prototypes for the string calls, and for xmalloc (which is behind the
> NEW macro).
I think I'm still confused as to why we're doing things this way.
Wouldn't it be much easier to just replace the calls to putenv() in the
Python linkage code with calls to setenv() and then not have to maintain
our own replacement? INN already uses setenv() all over the place.
Russ Allbery (rra at stanford.edu) <URL:http://www.eyrie.org/~eagle/>
More information about the inn-workers