Re: [Freeglut-developer] Testing: VS 2005

[John T. <nu...@me...>]

On Wed, Mar 11, 2009 at 08:57:57AM +0100, Sven Panne wrote:
> is always called on the copied string. But why should we copy the string at 
> all? I don't understand that... And what I understand even less: What is so 
> unsafe about using getenv()? The only thing that comes to my mind is that 
> getenv() is not required to be thread-safe, so a putenv() in another thread 
> might interfere. Is this Microsoft's reason behind this warning?

Those MSVC warnings of deprecation for the whole standard C library are
rediculus to say the least. I'd suggest you just ignore, or better yet
disable them.

-- 
John Tsiombikas (Nuclear / Mindlapse)
http://nuclear.sdf-eu.org/