🚀 go-pugleaf

In article <b2tJd455u610103u.iI@amdahl.uts.amdahl.com> kevin@amdahl.uts.amdahl.com (Kevin Clague) writes:
>
>One solution that is not exactly elegant, and certainly doesn't solve
>all the problems is to at least make sure that when someone opens the
>IEEE libs the opencnt is at least one.
>
>If I run a broken program and it doubly closes the IEEE libs, then opencnt
>is -1.  If I run this again then opencnt is < 1, at least force it to
>1.  This may not handle all the cases, but might help in some.
>

I don't think this is a good idea. If the opencnt ever goes negative
because of too many Closes, it is clearly an error condition. The sooner
we find out about error conditions the better.

I believe some sort of report must be generated when the opencnt goes
negative. This would prevent the case of a negative open count causing
an expunge by having the library reopened and a subsequent expunge
call performed when we run out of memory.

-- 
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.