Re: srfi-18 requirements

[Julian Graham]

Hi Neil,

> I haven't covered these yet.  Will try to soon, but could you resubmit
> anyway as a GIT commit patch, so that you end up being properly
> credited for the commit?

Yes -- find one attached.  As an aside, I've been having some
difficulty with git, specifically when it comes to backing out commits
that I've created prematurely (e.g., without git-adding the
ChangeLogs).  Do you guys have any recommendations for tools that add
a bit of sugar to the interface, or do I just have to buckle down and
learn the thing?


> Should m->level be set to 1 here?

Can I take it you're talking about the case in which a thread is
taking over an abandoned mutex that may have been locked more than
once, recursively, by the exited thread?  If so, yes -- m->level
should definitely be set back to 1.  Thanks for catching that!


> Regards, and thanks once again for your work on this area!

My pleasure!  Thank you for your continued patience.


Regards,
Julian

0001-Scheme-SRFI-18-implementation-and-tests-file.patch
Description: Text Data