stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Black (JIRA)" <>
Subject [jira] Closed: (STDCXX-104) [Mac OS X 10.2.8] Use of wcscoll and wcslen without checking guards
Date Wed, 30 May 2007 16:07:16 GMT


Andrew Black closed STDCXX-104.

    Resolution: Fixed

I'm not certain about the chronology, but
describes basically the same change as was described in the lose patch.  As such, I'm closing
the incident, though I no longer have the 10.2.8 operating system installed on the box I was
using when this incident was filed, so I'm unable to check how things compile on that operating
system at this time.

> [Mac OS X 10.2.8] Use of wcscoll and wcslen without checking guards
> -------------------------------------------------------------------
>                 Key: STDCXX-104
>                 URL:
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Build
>         Environment: Mac OS X 10.2.8/Darwin 6.8, GCC 3.1
>            Reporter: Andrew Black
>            Assignee: Andrew Black
>             Fix For: 4.2
>         Attachments: wcodecvt.diff
> In src/collate.cpp, collate_byname<wchar_t>::do_compare() uses wcscoll without
checking if _RWSTD_NO_WCSCOLL and/or _RWSTD_NO_WCSCOLL_IN_LIBC are undefined (my reading of
the macro names is that a version of wcscoll is availible if either is defined)
> In src/wcodecvt.cpp, __rw_libc_do_out uses wcslen().  As I read things, there should
be a macro pair _RWSTD_NO_WCSLEN and/or _RWSTD_NO_WCSLEN_IN_LIBC, but I don't think either
macro is defined/undefined in the generated config.h (I didn't think to bring it in after
the experiements over the weekend)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message