This is the mail archive of the
mailing list for the glibc project.
Re: inline __isctype no longer available for C++ programs
- From: "Ryan S. Arnold" <ryan dot arnold at gmail dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, Ryan S Arnold <rsa at linux dot vnet dot ibm dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 8 Aug 2013 11:39:31 -0500
- Subject: Re: inline __isctype no longer available for C++ programs
- References: <1375977352 dot 1294 dot 14 dot camel at localhost dot localdomain> <mvm4nb0cgg0 dot fsf at hawking dot suse dot de> <CAAKybw-e2VWJZEfJW09QqKObn1o81ntBLCk5xUk-KUJE84ZUUw at mail dot gmail dot com> <20130808163648 dot 4AB2E2C081 at topped-with-meat dot com>
On Thu, Aug 8, 2013 at 11:36 AM, Roland McGrath <firstname.lastname@example.org> wrote:
>> Is there a reason we can't provide an inline/optimized isctype?
> What we'd need is a very strong reason to provide such a nonstandard
> interface. There is no public interface that enshrines the notion of
> ctype classifications being represented by a bitmask.
I agree, and prior to the introduction of the isXXX inline/optimized
functions I can see why C++ programmers might have felt compelled to
use __isctype but I don't think there's a reason to encourage that