From owner-freebsd-questions Sun Sep 29 22:50:18 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CD0637B401 for ; Sun, 29 Sep 2002 22:50:17 -0700 (PDT) Received: from bsd4us.org (dsl-65-174-220-210.dslx.net [65.174.220.210]) by mx1.FreeBSD.org (Postfix) with SMTP id 605AB43E42 for ; Sun, 29 Sep 2002 22:50:16 -0700 (PDT) (envelope-from lyndon@gemini.bsd4us.org) Received: (qmail 18907 invoked by uid 1000); 30 Sep 2002 05:50:15 -0000 Message-ID: <20020930055015.18906.qmail@bsd4us.org> References: <20020930053326.18827.qmail@bsd4us.org> In-Reply-To: <20020930053326.18827.qmail@bsd4us.org> From: "Lyndon Griffin" To: freebsd-questions@freebsd.org Subject: Re: C++ symbol mangling Date: Mon, 30 Sep 2002 01:50:15 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lyndon Griffin writes: > The questions: > 1) Are the ctype.h definitions getting in the way? > 2) Is there a compiler flag to prevent this behavior? If so, what is it? > 3) Barring the compiler flag, could someone architect for me a macro or > two that would prevent this problem? Answering my own question, ctype.h is the culprit... it contains 2 macros that look like this: #define tolower(c) __tolower(c) #define toupper(c) __toupper(c) I'm working on some trickery to get around this, but any comments or suggestions are welcome. Sorry for the spam... <:) Lyndon http://bsd4us.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message