Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!bloom-beacon!eru!hagbard!sunic!news.funet.fi!uwasa.fi!ts
From: ts@uwasa.fi (Timo Salmi)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: v11i119: dartdemo, DART circuit simulation (part 01/03)
Message-ID: <1991Apr15.173424.10827@uwasa.fi>
Date: 15 Apr 91 17:34:24 GMT
References: <3646@sixhub.UUCP> <1991Apr11.175126.6881@isc.rit.edu> <1991Apr14.083252.16321@uwasa.fi> <1991Apr15.125532.22037@aplcen.apl.jhu.edu>
Followup-To: comp.lang.pascal
Organization: University of Vaasa
Lines: 24

In article <1991Apr15.125532.22037@aplcen.apl.jhu.edu> tcs@mailer.jhuapl.edu (Carl Schelin) writes:
>In article <1991Apr14.083252.16321@uwasa.fi>, ts@uwasa.fi (Timo Salmi) says:
:
>>I always include them within the executable code.  Much more
>>convenient for the user, and no potential hassle. 
>>
>
>While I did do this for one of my programs, the added memory taken by
>all the .chr and .bgi files increased my program over the small size
>(cga.bgi, egavga.bgi, gothic.chr). 

Ah!  But there is a catch here.  Only include the driver that you
are going to need.  E.g. on my more recent games I only include
egavga.bgi.  I make the assumption, that for a game the user has at
least an ega (fair enough nowadays).

But now we are drifting from the main theme of c.b.i.p.d, and I
have therefore put comp.lang.pascal as the followup-to.

...................................................................
Prof. Timo Salmi        
Moderating at garbo.uwasa.fi anonymous ftp archives 128.214.12.37
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun