| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Has anyone succeeded in interfacing to DECwindows from C++ using the OASYS compiler? We're having quite a time with it and have not yet succeeded. C++ has lots of problems with the DECwindows include files where C++ keywords are used freely among other things. Will anyone be updating those include files so that they are C++ compatible when DEC's C++ compiler comes out? Sue
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 132.1 | Second the motion! | DPDMAI::BEATTIE | But, Is BLISS ignorance? | Thu Jul 20 1989 12:57 | 15 |
I'd like to re-ask the .0 question with respect to the AT&T C++ pre-
processor, "cfront", which also complains tremendously about C++
reserved words being used as identifiers...
It is immediately and critically important for the project I'm on
to be able to use C++ via cfront (mandated by customer *sigh*).
I'd sure be happy to hear any advice on workarounds, or other
appropriate experience. I'm especially curious to hear an update
from Sue now that 5 months have gone by...
Drowning in the thick of it.
Brian.
| |||||
| 132.2 | DECWIN::JACKIE | Jackie Ferguson | Fri Jul 21 1989 08:43 | 6 | |
If I remember correctly, the C++ reserved words were only found in structure fields? If so, just rename them to be something else in your headers, you might want to do this conditionally, or use the vax bindings definitions for the structures. I don't know what MIT is coming up with to deal with the problem. | |||||