The _POSIX_THREAD_SAFE_FUNCTIONS Guard is only there for backwards
compatibility with programs that assume the functions are available if
pthread defines them, that's why there is an || separator
Not sure if we should force it to be defined as that should be done by
pthread ??
On Tue, Feb 3, 2015 at 11:25 AM, Jacek Caban <ja...@codeweavers.com> wrote:
> This seems logical that if we provide those, we should define it. That's
> also a clean way for applications to test for
> _POSIX_THREAD_SAFE_FUNCTIONS to detect presence of related functions.
>
> ---
> mingw-w64-headers/crt/time.h | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
