Nikos Mavrogiannopoulos wrote:
secure_getenv() has no (known to me) meaning for windows, and that's why I'd expect that call there to behave as getenv().
I'm afraid that this doesn't answer my question. I was asking why the behavior you expect would be more useful in practice than Gnulib's current behavior. (If secure_getenv has no known meaning for MS-Windows, then any implementation of it should be "correct" and there should be no reason to change from the current behavior. :-)
