From owner-freebsd-questions  Sun Aug 22 16:28:29 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from tim.Desert.NET (tim.Desert.NET [207.182.32.20])
	by hub.freebsd.org (Postfix) with ESMTP id 2D67414BDE
	for <freebsd-questions@freebsd.org>; Sun, 22 Aug 1999 16:28:27 -0700 (PDT)
	(envelope-from tim@tim.Desert.NET)
Received: (from tim@localhost)
	by tim.Desert.NET (8.9.3/8.9.3) id QAA14189
	for freebsd-questions@freebsd.org; Sun, 22 Aug 1999 16:26:58 -0700 (MST)
	(envelope-from tim)
Date: Sun, 22 Aug 1999 16:26:57 -0700
From: Thimble Smith <tim@desert.net>
To: FreeBSD Support List <freebsd-questions@freebsd.org>
Subject: ctype.h: #define _T 0x00100000L: how should it work?
Message-ID: <19990822162657.A14046@desert.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi.  I'm compiling omniORB2, which has the following code:

    /* in file initFile.cc */
    #include <ctype.h>

    /* ... now in another #included header, bootstrap.hh */

      class ObjIdList_var {
      public:
        typedef ObjIdList _T;
        typedef ObjIdList_var _T_var;

There are other places where the _T typedef is used.  ctype.h
has this definition:

    #define _T      0x00100000L             /* Special */

This obviously causes parse errors when I try to compile.  I can
easily fix this by adding #undef _T after every include of ctype.h.
There are other tricks that might be more elegant.  But I would
like to really fix things.  I guess I have 3 questions.

1)  Who is right?  Is it proper for omniORB to be using _T in their
    code?  Or is it right for FreeBSD to have _T defined in ctype.h?
    Or both, somehow?
2)  What, in the short term, is the best way to fix the problem?  I
    could add #ifdef SOME_IDENTIFIER ... #endif around that block of
    #defines in ctype.h.  I could add #undefs to the omniORB2 source
    code.  What have other people done for this type of thing?
3)  What is the best long-term solution?

Thanks for any help,

Tim


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message