Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!jato!jdickson
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: DOSBase
Message-ID: <1991Jun13.224411.26546@jato.jpl.nasa.gov>
Date: 13 Jun 91 22:44:11 GMT
References: <1991Jun13.072854.12241@disk.uucp> <1991Jun13.120849.26251@ira.uka.de>
Reply-To: jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 29

In article <1991Jun13.120849.26251@ira.uka.de> S_ASCHMIDT@iravcl.ira.uka.de (|S| Angela Schmidt) writes:
>In <1991Jun13.072854.12241@disk.uucp> specter@disk.uucp writes:
>
>> Does the dos library always need to be opened? I normally open it, but I noticed
>> that I forgot one time and it worked fine with the DOS calls. (I think I was
>> using Delay() ) I guess it is poor practice not to open it, since if all dos
>> using processes were gone you would be out of luck correct?
>> 
>> Byron
>
>The dos.library will be opened while executing the bootblock of a booting
>disk. So it is open when your program starts. But you should open it
>yourselve, since otherwise you can't tell OpenLibrary which versionnumber
>you need.

	I think that the more important point here is that opening the DOS
library prevents it from going away. 

 And it's no nice style not to open and close it. Even if some
>C-startups think it's not necerssary to close it....
					  ^^^^

	They're broken then if the DOS library isn't closed when the program
exits.
>
>> -- 
>> Byron 'Maxwell' Guernsey
>
-jeff