Xref: utzoo comp.os.msdos.apps:824 comp.os.msdos.misc:922 comp.os.msdos.programmer:2641
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!rex!uflorida!reef.cis.ufl.edu!jdb
From: jdb@reef.cis.ufl.edu (Brian K. W. Hook)
Newsgroups: comp.os.msdos.apps,comp.os.msdos.misc,comp.os.msdos.programmer
Subject: TC++ bug(?)
Message-ID: <26152@uflorida.cis.ufl.EDU>
Date: 4 Jan 91 01:01:59 GMT
References: <15789.277ce62a@levels.sait.edu.au> <1008@pdxgate.UUCP> <6082@ncsugn.ncsu.edu>
Sender: news@uflorida.cis.ufl.EDU
Organization: UF CIS Dept.
Lines: 21

I was writing a simple demo program today using TC++.  nothing fancy, nothing
special....worked just fine when I compiled within TC.  To get smaller code
(read: No debug) I tend to exit then run TCC.  Thus, this program, which
uses graphics:

TCC demo

works within the environment.  But I ran TCC and then tlink, tried a couple
of switches (to see if it would open the graphics.lib) and guess what?  It
trashed GRAPHICS.LIB and about half o f my libraries, probably because of
an incorrect switch (tlink has CRAPPY documentation).  I did link in a
.BGI and .CHR file into the .LIB after running BGIOBJ.

This, to me, is not very good.  Graphics.lib ended up being 2048 bytes.
Oh, after adding the .BGI and .CHR file, it still worked fine.  It was
when I compiled and linked from the command line that my LIB directory
got eaten ALIVE.

anyone have any ideas?

Brian