[ By Archive-name
| By Author | By Category | By Newsgroup ]
[ Home | Latest Updates | Archive Stats | Search | Usenet References | Help ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 7 of 9)
Previous Document: 230) Is there a C++ binding for Motif?
Next Document: 232) How can I have a C++ member function in a callback?
[ Home | Latest Updates | Archive Stats | Search | Usenet References | Help ]
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 7 of 9)
Previous Document: 230) Is there a C++ binding for Motif?
Next Document: 232) How can I have a C++ member function in a callback?
231) How can I avoid C++ String class and typedef char *String
conflicts? We're using the USL C++ Standard Components which has the String class. This, however, conflicts with the typedef char *String found in <X11/Intrinsic.h> [Last modified: Oct 94] Answer: This is very simple to workaround. I agree that it is "wrong" but all you need to do is: #define String XtStringType #include "all the X files" #undef String This will translate the offending symbol. Thanks to Doug Rand <drand@sgi.com>
Top Document: Motif FAQ (Part 7 of 9)
Previous Document: 230) Is there a C++ binding for Motif?
Next Document: 232) How can I have a C++ member function in a callback?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ By Archive-name | By Author | By Category | By Newsgroup ]
[ Home | Latest Updates | Archive Stats | Search | Usenet References | Help ]
Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)
Last Update July 09 2008 @ 00:14 AM