> > Nikos Mavrogiannopoulos wrote:
> > The current implementation doesn't have any support for windows,
> > meaning that environment variables will be unusable on that OS.
>
> Why is that the wrong thing to do? Can you give an example? Why would
> an application invoke secure_getenv on MS-Windows?
secure_getenv() is targeted for libraries rather than end-applications.
A library will call secure_getenv() to act on some variable because it
is the reasonable thing to do on UNIX systems. However, secure_getenv()
has no (known to me) meaning for windows, and that's why I'd expect
that call there to behave as getenv().
That way a library will simply call (when used with gnulib):
var = secure_getenv("MYENV");
and would work as expected in UNIX and windows systems.
regards,
Nikos
PS. Please keep me in CC as I'm not subscribed in the mailing list.
