Re: unresolved external symbol _asctime_r then (unresolved external symbol _asctime_r)

At 9:36 AM -0800 3/14/04, Brent \"Dax\" Royal-Gordon wrote:
>DH wrote:
>>I'm on Win2000 SP4  compiling with MSVS6 SP5
>>I cd to parrot, run perl Configure.PL, then nmake, and I'm faced with
>
>These are known issues with Parrot on Win32.  The Parrot guys are 
>working on it.
>
>The _r function calls are reentrant versions of the normal calls. 
>You apparently have to use them on Unixen for thread safety.  MS 
>took a different tack--they provided a thread-safe version of their 
>C library.  Basically, someone shoved in threading without thinking 
>about how it worked on Windows, which turns out to be rather 
>different from Unixen. Oops.

I did that, actually, and I was well aware of what it'd do. The C89 
spec declares the base types (asctime and friends) as non-reentrant 
and non thread-safe. The _r versions are threadsafe, but they're also 
not C89 standard. (SUSv2 defines them, FWIW) Didn't know what Windows 
(or any non-SUSv2) platform defined them as so I decided to break it 
and let the folks with platforms where it was an issue fix it.
-- 
                                         Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[email protected]                         have teddy bears and even
                                       teddy bears get drunk