Lars Balker Rasmussen (via RT) <[EMAIL PROTECTED]> writes:
> There's no reason to test for the presence of setenv/unsetenv in libc
> - these functions are emulated if not present.
I'll just reiterate: Configures test for the presence of setenv and
unsetenv should not cause env.t to to skip the env tests! They are
entirely different layers of execution, and if the functions are not
present, they are emulated.
If the emulation doesn't work, we want to know about it, viz:
> However, now the 4th test fails on Solaris (and most likely other OS's
> witout setenv/unsetenv). This is because the test relies on a key
> disappearing from %ENV when it's been unsetenv'ed - this doesn't
> happen when using putenv("key=") as the current unsetenv emulation.
>
> I'm not sure what's the best portable way to handle this is.1
Any comments?
--
Lars Balker Rasmussen Consult::Perl
