From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19211 invoked by alias); 15 Jun 2004 18:28:39 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 19057 invoked from network); 15 Jun 2004 18:28:32 -0000 Received: from unknown (HELO mhub-c4.tc.umn.edu) (160.94.128.34) by sourceware.org with SMTP; 15 Jun 2004 18:28:32 -0000 Received: from nnxpubwytgvj3u (x128-101-250-24.dialup.umn.edu [128.101.250.24] (may be forged)) by mhub-c4.tc.umn.edu with ESMTP; Tue, 15 Jun 2004 13:28:29 -0500 (CDT) X-Umn-Remote-Mta: [N] x128-101-250-24.dialup.umn.edu [128.101.250.24] #+HF+LO+TS+AU Message-ID: <007801c45306$7fed16d0$18fa6580@nnxpubwytgvj3u> From: "Nikolai Nezlobin" To: Cc: "Eljay Love-Jensen" , References: <000501c451ad$6465ed10$8efa6580@nnxpubwytgvj3u><6.1.1.1.0.20040614073947.0207b7b8@iplan-mn.corp.adobe.com><002501c45261$7e08fc80$94f96580@nnxpubwytgvj3u><6.1.1.1.0.20040614190954.02138bc0@iplan-mn.corp.adobe.com><002301c4529c$ddf95fa0$e2fd6580@nnxpubwytgvj3u> Subject: Re: isalnum not declared Date: Tue, 15 Jun 2004 18:28:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00151.txt.bz2 Please see my comments below. | "Nikolai Nezlobin" writes: | | > Eljay, | > | > 'isalnum' is not my function, it is the part of namespace std and the GNU | > project, right? | | isalnum is not necessarily part of the GNU project. GCC expects the | standard C library to be provided by the target platform. cygwin, | mingw (both windows platforms), MacOS X, [free|net|open]bsd, aix, | solaris, hpux, and many others provide C libraries which have | nothing to do with the GNU project, and are not under the control | of GCC, or any GNU people. | | Only on linux and hurd are functions such as isalnum part of a GNU | project (and in those cases, they are part of the glibc project, | not the GCC project). I meant that 'isalnum' and cctype are not home-made (Eljay seemed to think this way). They were downloaded when I installed Linux. If I write #include in cctype then an error occurs in some file included from locale_facets.h, but the compiler goes through using::isalnum in cctype. I would not consider changing cctype as a good solution unless the changes came from someone associated with the gnu / glibc project. | | > Compiler says that isalnum is not declared in the following line in cctype: | > | > namespace std | > { | > using ::isalnum; | > ... | > } | > | > I think this is very embarrassing. | | 'embarrassing' ? It is unfortunate that you have encountered a | problem, and more unfortunate still that no-one has yet solved your | problem, but I can't see anything 'embarrassing' about it - it | isn't as if somebody was caught lying about uranium sales or some | such. If you wish, I will not use the word "embarrassing" anymore. I needed it to attract attention to the error message that I received. I do not understand how 'isalnum' can be undeclared in cctype. I will try to reduce the code to the minimum. | | > Doesn't cctype refer to all the | > necessary files, including the one that defines isalnum? | | ? | | #include | | int main() | { | return std::isalnum('['); | } | | compiles and runs correctly with g++ 2.95.3, 3.2.2, 3.3.3, and 3.4 | on i686-freebsd5.2 and i386-slackware-linux . | | If you were using any other linux distro, I would guess you had not | installed the [g]libc-devel package, since most other linux | distros do not include headers in the ordinary glibc package. But | looking at a slackware 9.0 box (where I cannot reproduce the problem | you report) I see that the package glibc-2.3.1-i386-3 contains the | standard C header files. Maybe. The error message is that 'isalnum' is not declared, not that some file was not found though. | |