Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Message-ID: <630749108.1137437121204.JavaMail.jira@ajax.apache.org>
Date: Mon, 16 Jan 2006 19:45:21 +0100 (CET)
From: "Andrew Black (JIRA)" <jira@apache.org>
To: stdcxx-dev@incubator.apache.org
Subject: [jira] Updated: (STDCXX-104) [Mac OS X 10.2.8] Use of wcscoll and
 wcslen without checking guards
In-Reply-To: <351881478.1136829444452.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/STDCXX-104?page=all ]

Andrew Black updated STDCXX-104:
--------------------------------

    Attachment: wcodecvt.diff

>From my prospective, this item is nearly resolved.

Attached is a one line change, replacing an instance of wcslen with _RWSTD_WCSLEN that was missed when such things were changed in a previous commit.

> [Mac OS X 10.2.8] Use of wcscoll and wcslen without checking guards
> -------------------------------------------------------------------
>
>          Key: STDCXX-104
>          URL: http://issues.apache.org/jira/browse/STDCXX-104
>      Project: STDCXX
>         Type: Bug
>   Components: Build
>  Environment: Mac OS X 10.2.8/Darwin 6.8, GCC 3.1
>     Reporter: Andrew Black
>     Assignee: Martin Sebor
>  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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira