Xref: utzoo comp.lang.c++:9266 comp.sys.ibm.pc.misc:1193 alt.msdos.programmer:2091
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!emory!mephisto!mcnc!ncsuvx!ncsuvm!ucf1vm!popovich
From: POPOVICH@ucf1vm.cc.ucf.edu (Peter Edward Popovich)
Newsgroups: comp.lang.c++,comp.sys.ibm.pc.misc,alt.msdos.programmer
Subject: Re: On Linking TC++ to Assembly Language
Message-ID: <90239.223422POPOVICH@ucf1vm.cc.ucf.edu>
Date: 28 Aug 90 02:34:22 GMT
References: <1990Aug20.143139.7100@ux1.cso.uiuc.edu>
Organization: University of Central Florida--Computer Services
Lines: 34

In article <1990Aug20.143139.7100@ux1.cso.uiuc.edu>, khan@ux1.cso.uiuc.edu
(Scott Coleman) says:
>My guess is that TC++ is doing some really intense type checking, and because
>the symbols in the .ASM modules don't match EXACTLY with the symbols that
>the C++ modules in the library are looking for, TLink gets upset.
>
>How can I work around this? Ideally, I would like to insert the "extra"
>parameter information which is lacking for the .ASM modules. Frantic
>scanning of the many TC++ manuals reveals no obvious way to do this, and
>the section on linking TC++ with .ASM doesn't even mention the problem.
>If I can't insert the parameter type info, can I force TLink to relax
>its type checking on those .ASM modules? Is there another solution?

Since you have TC++, I'll direct you to look at the header files. Note how
they all have stuff (approxamately) like:

#ifdef cplusplus
struct c {
#endif
char *srtcpy(char *,char *);
#ifdef cplusplus
}
#endif

Please Note: This is an example only! Look at the actual header files, you'll
see what actually should be there!

If you enclose the function definitions in an identical struct, TC++ will
expect the old style (non-OOP) object module for that function.

Have Fun!

Peter E. Popovich -- POPOVICH@UCF1VM.BITNET -- popovich@ucf1vm.cc.ucf.edu
List Owner, TURBOC-L@UCF1VM -- #include <stddisclaim.h> -- "Who, me?"