This is the mail archive of the
mailing list for the glibc project.
[Bug libc/25214] ctype.h performance (and potentially behavior) depends on include order
- From: "travis.downs at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 22 Nov 2019 01:46:58 +0000
- Subject: [Bug libc/25214] ctype.h performance (and potentially behavior) depends on include order
- Auto-submitted: auto-generated
- References: <email@example.com/bugzilla/>
--- Comment #2 from Travis Downs <travis.downs at gmail dot com> ---
Yes, I'm compiling as C++, and I should have made that clear from the start.
In C, the flow is totally different and toupper/tolower are macros, not
functions (as you pointed out).
Although I'm compiling as C++, the only headers I'm including are <stdlib.h>
and <ctype.h>. I'm not sure exactly where __NO_CTYPE is getting defined in this
case, but in another case I looked at (this time including C++ headers like
<algorithm>, the __NO_CTYPE definition came from <bits/os_defines.h>).
You are receiving this mail because:
You are on the CC list for the bug.