[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: An actual NSLock bug
|
From: |
Adam Fedor |
|
Subject: |
Re: An actual NSLock bug |
|
Date: |
Sat, 22 Oct 2005 21:29:30 -0600 |
Well, sure, I don't think we should forbid a developer from doing
something crazy if they really want to. Particularly in this case since
there is no work-around when the exception is called. Perhaps changing
the exception to a warning (GSOnceMLog). Any opinions?
On Oct 21, 2005, at 8:36 PM, Morgan Giddings wrote:
To that end, in my own version of Gnustep, I commented out a single
line in NSLock that does the check, and this part of the code works
fine (though there are some other issues still). I would rather move
forward with this port, and get the software (gfs.unc.edu) out there
to people on Windows and Linux, than to be held up further by this
issue... but, if I still haven't convinced anyone, I suppose at some
point I will have to come back and deal with this...