C/C++ and visibility

New Message Reply Date view Thread view Subject view Author view

Wear, Mark (mark.wear++at++lmco.com)
Tue, 17 Nov 1998 15:58:30 -0700


Please Help...

I have modified the source code for the pdfBreakup routine, shipped with
Performer 2.2, to better meet my needs. This routine uses Performer C API.
Much of my vast application has been developed in C++. It has become
necessary to call a C++ function from within this breakup routine. The C++
function actually needs to be registered as a traversal callback. Changing
the breakup routine's extension from .c to .c++, adjusting the makefile, and
including a token to force the compiler to recognize Performer C API, I was
able to get my version of the breakup routine to compile. My problem occurs
when I try to link. Both the breakup function call and the C++ callback are
listed as unresolved text symbols. I have checked the prototypes and they
appear correct. I believe my problem to be caused by some sort of C/C++
visibility issue, even though all of my files are currently being compiled
as C++. Does the C_API token I used to make the Performer C API visible do
more than just that? Any ideas? Is there a way to call a C++ routine from a
C function? (this would also solve my problem)

Also, the C++ callback contains Vega API.

Thanks,
Mark
Mark E. Wear
Electronic Systems Engineer
Lockheed Martin Vought Systems
mark.wear++at++lmco.com
(972) 603-2758


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Tue Nov 17 1998 - 15:00:09 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.