Date: Sun, 16 Nov 2014 11:19:51 -0700
From: Matt Birkholz <m...@birchwood-abbey.net>
> From: Taylor R Campbell <campb...@mumble.net>
> Date: Thu, 13 Nov 2014 22:41:47 +0000
>
> Does anyone rely on recursion in WITH-THREAD-MUTEX-LOCKED? I would
> like to prohibit recursive thread mutex locks altogether,
Sounds good to me.
OK.
> and prohibit the use of THREAD-MUTEX-OWNER except as a diagnostic
> and debugging feature.
How? If it is not exported to (), I will need to type
(define thread-mutex-owner
(access thread-mutex-owner (->environment '(runtime thread))))
in my debugging session?
I meant by a sternly-worded message in the documentation and/or
comments.
Can we "fix" ACCESS to do the coercion? I'd rather type
(define thread-mutex-owner (access thread-mutex-owner '(runtime thread)))
I'd rather nix ACCESS and redo the way environments work, but I'm not
volunteering for that.
_______________________________________________
MIT-Scheme-devel mailing list
MIT-Scheme-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/mit-scheme-devel
