🚀 go-pugleaf

I was just cruising through some software today, and noticed that many, many,
programs leave the dos.library open after exiting.  In fact, it seems to be
a majority in the (limited) sample of stuff I tested, mostly PD.  Upon looking
further, I find that my Manx 'C' 3.4 compiler seems to generate programs that
open the dos.library, but never seems to close it upon exit.  If most folks
where using the Manx compiler (or if Lattice did it also) I can see that this
would indeed leave open copies of dos.library around upon exit.  One would
assume that the compiler startup code would Close() anything that was Open()ed.
Is this a bug, or am I missing something?  I am in the process of ripping
apart the actual startup code that Manx links in, but my disassembler seems
to find no place where the library is closed.  Why is this?

I guess the other option is that Xoper is lying to me and there really aren't
multiple opennings of dos.library around (not very likely).


    -dave