Xref: utzoo comp.compilers:1072 comp.os.msdos.programmer:225
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!know!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!snorkelwacker!spdcc!esegue!compilers-sender
From: bnrgate!bwdls58.bnr.ca!mlord@uunet.UU.NET (Mark Lord)
Newsgroups: comp.compilers,comp.os.msdos.programmer
Subject: Re: MicroSoft C 6.0F
Keywords: graphics
Message-ID: <1990Jul24.234408.10478@esegue.segue.boston.ma.us>
Date: 24 Jul 90 23:44:08 GMT
References: <325@tygra.ddmi.com> <1990Jul19.182239.6948@esegue.segue.boston.ma.us>
Sender: compilers-sender@esegue.segue.boston.ma.us
Reply-To: bnrgate!bwdls58.bnr.ca!mlord@uunet.UU.NET (Mark Lord)
Followup-To: comp.os.msdos.programmer
Distribution: na
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 19
Approved: compilers@esegue.segue.boston.ma.us

In article <1990Jul19.182239.6948@esegue.segue.boston.ma.us> 6600sirt@ucsbuxa.ucsb.edu (Mike O'Brien) writes:
>
>The big difference, though, is that MSC does not use the equivalent of
>BGI files.  All of the graphics support (exept fonts) is linked into
>the EXE.  On the plus side, that means you don't have to distribute
>BGI files with everything you write.  On the down side, it means that
>you can't modify MSC's functions to work with Super VGA or anything.

Actually, .BGI files can also be linked into the .EXE by using a turbo
utility to first convert the ones you want to use into .OBJ format, 
and then simply linking them in.  Check out the Turbo-C docs for details.

-- 
 ___Mark S. Lord__________________
| ..uunet!bnrgate!bmerh614!mlord |
| ..uunet!bnrgate!mlord%bmerh614 |
-- 
Send compilers articles to compilers@esegue.segue.boston.ma.us
{spdcc | ima | lotus| world}!esegue.  Meta-mail to compilers-request@esegue.