🚀 go-pugleaf

[]

When you write a program that opens a GEM virtual workstation, you
need to close it (with v_clsvwk()) before you exit the program.  If you
don't, GEM keeps that workspace open, and opens a _new_ one next time
you run the program.  Eventually it runs out of "handles" and wierd
things happen.  You then have to reboot.

The problem is: if your program crashes unintentionally, without doing
the v_clsvwk(), you're in trouble!  Question: can you close it later,
without knowing the handle number?  Is there a way to find out whether
virtual workstations are open and what their handles are?  Is it safe
to call v_clsvwk() on a fictitious handle?  What handle numbers would
be good guesses to try and close?  (If all else fails, you might want
to have your program print out the handle numbers (to a file?) while
in debugging phase.)

- Moshe Braner