NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/lang/pascal/5170

Text File | 1992-09-02 | 1.6 KB | 37 lines

Newsgroups: comp.lang.pascal
Path: sparky!uunet!sun-barr!cs.utexas.edu!torn!news.ccs.queensu.ca!mast.queensu.ca!dmurdoch
From: [e-mail] (Duncan Murdoch)
Subject: BGI environment variables (was:  Executables)
Message-ID: <[e-mail]>
Lines: 25
Sender: [e-mail] (Netnews control)
Organization: Queen's University
References: <[e-mail]> <[e-mail]>
Date: Wed, 2 Sep 1992 13:41:40 GMT

In article <[e-mail]> [e-mail] (Foster Schucker) writes:
>> Why should I have to put up with 640x200x2 (or 320x200x4) when my hardware
>> can do 640x200x16 *and* I have the BGI to do it? Folks with superVGA
>> probably feel the same.
>>
>> And we'd *all* like to be able to eliminate the space used by the unused
>> BGI drivers.
>>
>> Oh yeah, Borland should have "suggested" an environment variable to point
>> to the directory with all your BGI files. <sigh>
>
>I love it, what a great idea!!  I'm going to write to all the authors
>of the programs and suggest that they look at the "BGI" environment
>var and use that.

I agree - it's a great idea.  But don't we need two variables?  One to name
a special driver, and one to give the directory for BGI files in general?

I'd suggest names, but I think it's better to pick something that's already
in common use.  I've never released or much used graphics programs, so it's
up to those of you who do:  what variables are currently in use for these
purposes?  Is there already a consensus of what the names should be?

Duncan Murdoch
[e-mail]