home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.apollo
- Path: sparky!uunet!sun-barr!ames!think.com!paperboy.osf.org!paperboy!drand
- From: drand@spinner.osf.org (Douglas Rand)
- Subject: Re: C++ V2.1.0 versus OSF/Motif ANSI/NON-ANSI. Help needed
- In-Reply-To: pfander@kommu.UUCP's message of 21 Jul 92 10:01:15 GMT
- Message-ID: <DRAND.92Jul21135935@spinner.osf.org>
- Followup-To: comp.sys.apollo
- Sender: news@osf.org (USENET News System)
- Organization: Open Software Foundation
- References: <510@kommu.UUCP>
- Date: 21 Jul 92 13:59:35
- Lines: 26
-
- In article <510@kommu.UUCP> pfander@kommu.UUCP (Dr Gotthard Pfander) writes:
-
- C++ V2.1.0 as supplied by HP/Apollo uses ANSI-calling convention as default.
-
- The supplied libraries: libC.a, libOstream.a, ... all expect ANSI-calling.
-
- Using OSF/Motif, being NON-ANSI as supplied by HP/Apollo,
- thus creates a serious compatibility-problem.
-
- Using C++ requires at least the library libC.a for the _main an similar things.
-
- Anyone got a good idea, how to solve this decently.
-
- Please, don't tell me things like RTFM ....
-
- Oh. But that's my favorite answer. Try including the include
- files in a extern "C" { ... } block so you get K&R C compliance.
- You might need extern "C--" for some C++ compilers. Motif 1.1.x
- included ANSI prototypes, so I'm not sure why HP would have
- stripped them. I'm presuming you're not using Motif 1.0.
-
- --
- Douglas S. Rand <drand@osf.org> OSF/Motif Dev.
- Snail: 11 Cambridge Center, Cambridge, MA 02142
- Disclaimer: I don't know if OSF agrees with me... let's vote on it.
- Amateur Radio: KC1KJ
-