>> Yes, Solaris sucks for removing setenv(3), but that doesn't mean EPIC >> should implement it without supporting putenv(3) or something which >> Solaris does support :) >> Unsure whether this latest change breaks SunOS 4.x support too.. > >putenv() is POSIX while setenv() is a BSDism... putenv() should be more >widely supported anyway, so I'm not sure why we're using setenv()
The semantics for putenv() pretty much require that any program using it suffer memory leaks. Furthermore, without unsetenv(), there is no way to portably remove an environment variable, so it's just plain stupid to remove that. Setenv() and unsetenv() are historical unix functions (from v7) and it blows my mind that solaris would stop supporting v7 functions. I guess sun isn't too interested in "portability" of unix programs. Too bad. Jeremy _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
