Anybody experienced this problem with MSC7.0 linker?

Article View: comp.windows.ms.programmer

Article #26

Back to comp.windows.ms.programmer Previous Next

#26

From: yongqi yang;S10000
Date: Wed, 22 Jul 1992 03:20

11 lines
1365 bytes

I am converting one of my old C++ program from BC code base to MSC7.0. The 
program got compiled fine. When I tried to link it, I got some error message 
from the MSC linker, complaining some exported class member 
functions have no internal representation, error L2022. 
BTW, the program is a DLL. I dump the map file, and after several
minutes checking, I found all those functions that the Linker complains had 
very long names, and been assigned to 0000:0000. So I did some test by reducing
the length of the name of some member functions, and fixed some complains. On
the other hand, the program was compiled and linked under Borland C++ fine.  I
wonder if anybody else experienced this kind of problem. It seems to me MSC7.0
linker doesn't handle long function name very well.

Technical Details

Message-ID: <1992Jul22.032027.22518@serval.net.wsu.edu>

Path:

arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!ubc-cs!uw-beaver!news.u.washington.edu!serval!wsuaix.csc.wsu.edu!yyang

References: <1992Jul14.120346.2899@Informatik.TU-Muenchen.DE>

Show Full Headers

Complete Article Headers

Newsgroups: comp.windows.ms.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!ubc-cs!uw-beaver!news.u.washington.edu!serval!wsuaix.csc.wsu.edu!yyang
From: yyang@wsuaix.csc.wsu.edu (yongqi yang;S10000)
Subject: Anybody experienced this problem with MSC7.0 linker? 
Message-ID: <1992Jul22.032027.22518@serval.net.wsu.edu>
Sender: news@serval.net.wsu.edu (USENET News System)
Organization: Washington State University
References: <1992Jul14.120346.2899@Informatik.TU-Muenchen.DE>
Date: Wed, 22 Jul 92 03:20:27 GMT
Lines: 12

Reply to Parent Message