🚀 go-pugleaf

In article <b03Kac9bnd10108qAIk@amdahl.uts.amdahl.com> kevin@amdahl.uts.amdahl.com (Kevin Clague) writes:
>In article <1356@percival.UUCP> billc@percival.UUCP (William Coldwell) writes:
>
>
>So if you are working with Manx (maybe lattice too) and you are
>explicitly opening the IEEE library, then when you close the library,
>set the global library pointer to NULL (so Manx doesn't close it a
>second time).
>
>I wrote Dale Luck about this bug and he says it's a Manx bug.  I think
>that the CloseLibrary code should never let the open count go negative,
>but I was unable to convince Dale of this.  So you must fix it yourself.
>
It is definately a Manx bug. However CloseLibrary not letting the
Opencount go negative and returning would only postpone an inevitable
crash. The fact is, the program opened the library once and now closed
it twice. Very Bad.

The one change we could make for V1.4 is have it GURU (recoverable?)
when the opencount goes negative. The system is definately sick and
we cannot continue normal operation of the system software. If someone
else has the library open and tries to access it when your manx program
has just caused a flush would result in fire works also.

A more complex change would be the ieee library keeping a table of
what tasks have opened the library. It could then keep a global count
in the standard place, and when an individual task closes, make sure
it is not doing something bad. It could then at least insure the
correctness of master opencount.

-- 
Dale Luck     Boing, Inc. {cbmvax|oliveb|pyramid}|!amiga!boing!dale
Although I do contract work for Amiga-LosGatos, my opinions probably
don't represent those of Commodore or its management or its engineers,
but I think the world would be a better place if they did.