I personally like using getenv, setenv, and unsetenv. The documentation could be changed to say something like passing .NIL will delete the environment variable on those systems that support the unsetenv(3) call.

On my man page it says

putenv() no longer copies its input buffer. This often appears in crash logs as a crash ingetenv(). Avoid passing local buffers or freeing the memory that is passed toputenv(). Usesetenv(), which still makes
an internal copyofits buffers.

So it sounds like setenv, is much safer. In looking at how setenv and unsetenv are implemented, they are thread safe, as they use locks to prevent concurrent update to the Environment pointers array.

Bruce
On Oct 1, 2009, at 10:26 AM, Mark Miesfeld wrote:

On Thu, Oct 1, 2009 at 10:23 AM, Rick McGuire <[email protected]> wrote:

I'd say leave the 4.0 branch alone, open the bug, and do a complete
cleanup of this area to use more "modern" methods.  That gives us a
little more time to catch the gotchas.

Good, that's exactly what I was thinking.

--
Mark Miesfeld

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to