GNU bug report logs - #48949
28.0.50; Thread-Process Liberalization

Previous Next

Full log

View this message in rfc822 format

From: dick.r.chiang <at> gmail.com
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 48949 <at> debbugs.gnu.org
Subject: bug#48949: 28.0.50; Thread-Process Liberalization
Date: Sat, 12 Jun 2021 10:51:45 -0400

EZ> why not unlock the process, so that its output could be
EZ> processed by any thread?

Yes, why don't I just call pset_thread(proc, Qnil) when the mood strikes in
process.c?  You make it sound as if pset_thread is an exposed defun.

Nine years ago, tromey in commit 6c0d5ae declaimed the notion of locking a
thread to a process.  Other than raising an error when a thread tried to
accept output from a process not its own, there appears to my untrained eye
no other ramification, good or bad, of pset_thread.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.