home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.pascal
- Path: sparky!uunet!mcsun!sunic!kth.se!kjell
- From: kjell@weber.e.kth.se (Kjell Rilbe)
- Subject: Re: BGI Env variable
- Message-ID: <1992Sep11.125327.20440@kth.se>
- Sender: usenet@kth.se (Usenet)
- Nntp-Posting-Host: weber.e.kth.se
- Organization: Dept. of EE, Royal Institute of Technology, Stockholm, Sweden
- References: <2148.2AAF90B7@catpe.alt.za>
- Date: Fri, 11 Sep 1992 12:53:27 GMT
- Lines: 26
-
- In article <2148.2AAF90B7@catpe.alt.za> Louis.Mandelstam@p2.f42.n7101.z5.fidonet.org (Louis Mandelstam) writes:
- >.....
- >BTW is the idea that all the BGI drivers should be in the directory, or
- >would it be better to link the common drivers into the EXE (EGAVGA, HERC etc)
- >and have an option for the user to specify an external driver which would
- >then be located in the directory specified by the BGI enviroment variable?
- >
- >Cheers
- >The Poltergeist
- >
- I like the idea of environment var for BGI:s.
-
- Wouldn't it be best to fo it this way: Let the program check for the
- environment variable BGI, and if it exists, use the BGI it sepcifies,
- otherwise use the built-in autodetect to find which one of the standard
- (and linked-in) BGI:s to use.
-
- Just a thought...
-
- /Kjell Rilbe
-
- --
- -----------------------------------------------------------------------------
- ! Kjell Rilbe ! Love is not about getting everything on the list, !
- ! kjell@elixir.e.kth.se ! it's about accepting the things that aren't on !
- ! ! the list! - Stewart Markowitz, LA Law !
-