My bad - setenv() will 'work' on win32 to modify the program's 'C' environment table. Where it falls down is modifying the 'inherited' environment, which must be maintained with SetEnvironmentVariable. Why setenv() on Win32 didn't do this has always puzzled me.
By the way, it's _setenv() on win32, unless you link oldnames.lib.
But apr_env_set() does the right thing I suppose...
But I'm liking Justin's comment that creating "a pool of our own" based on the NULL pool might be the way to go. Some pools need to last a lifetime.
Lots of storage for a flag. And how do you maintain addressibility to the pool across unload/reload of the DSO?
