Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.programmer
Subject: Re: What is __acrtused?
Message-ID: <274129c2@ralf>
Date: 14 Nov 90 10:25:54 GMT
Sender: ralf@b.gp.cs.cmu.edu
Organization: Carnegie Mellon University School of Computer Science
Lines: 20
In-Reply-To: <1990Nov13.164250.19569@geac.com>

In article <1990Nov13.164250.19569@geac.com>, huehn@geac.com (Robert Huehn) wrote:
}I've ran into this too, with MSC 5.1.  It's a little annoying.  If you take
}a look at the assembly file MSC generates, the first line in the externals
}list is:
}
}EXTRN  __acrtused :ABS
}
}It isn't used in the rest of the listing either.  So it seems that you could
}safely give the linker a bogus reference in your assembly code.  It works
}for me.

My understanding is that the only thing this symbol does is force the C
startup code to be pulled in from the library.	Turbo C requires that the
startup module be given explicitly on the linker command line, while MSC
includes the startup module in the library.
--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=- 412-268-3053 (school) -=- FAX: ask
ARPA: ralf@cs.cmu.edu  BIT: ralf%cs.cmu.edu@CMUCCVMA  FIDO: 1:129/3.1
Disclaimer?    |   I was gratified to be able to answer promptly, and I did.
What's that?   |   I said I didn't know.  --Mark Twain