From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: Richard M Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: multi-threaded Emacs
Date: Wed, 10 Dec 2008 13:18:26 -0500
Message-ID: <E1LATdi-00058t-LX@fencepost.gnu.org>
References: <87abbiody1.fsf@master.homenet>
	<E1L6pOD-0005Gc-Pz@fencepost.gnu.org> <877i6l5d8s.fsf@master.homenet>
	<E1L79QM-0006J3-Lp@fencepost.gnu.org> <874p1npvtj.fsf@master.homenet>
	<E1L7Xhu-0006DQ-HE@fencepost.gnu.org>
	<jwvfxl643rk.fsf-monnier+emacs@gnu.org> <87ej0qci8g.fsf@master.homenet>
	<jwvk5aim29a.fsf-monnier+emacs@gnu.org> <87y6yxm7xr.fsf@master.homenet>
	<jwv1vwpxbni.fsf-monnier+emacs@gnu.org>
	<E1L8QuF-00045t-1q@fencepost.gnu.org>
	<jwvy6yur63e.fsf-monnier+emacs@gnu.org>
	<E1L92mr-0000oK-PR@fencepost.gnu.org> <87hc5gyn9x.fsf@master.homenet>
	<E1L9koi-0001ou-Qz@fencepost.gnu.org> <87ej0ixx97.fsf@master.homenet>
	<E1LA6Ls-0001Oh-R1@fencepost.gnu.org> <87myf5p3ki.fsf@master.homenet>
Reply-To: rms@gnu.org
NNTP-Posting-Host: lo.gmane.org
Content-Type: text/plain; charset=ISO-8859-15
X-Trace: ger.gmane.org 1228933225 25375 80.91.229.12 (10 Dec 2008 18:20:25 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Wed, 10 Dec 2008 18:20:25 +0000 (UTC)
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
To: Giuseppe Scrivano <gscrivano@gnu.org>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 10 19:21:28 2008
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([199.232.76.165])
	by lo.gmane.org with esmtp (Exim 4.50)
	id 1LATgd-0003bw-96
	for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2008 19:21:27 +0100
Original-Received: from localhost ([127.0.0.1]:46926 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1LATfR-0006iV-Sr
	for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2008 13:20:13 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LATeL-0006QK-7X
	for emacs-devel@gnu.org; Wed, 10 Dec 2008 13:19:05 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LATeJ-0006Pg-J5
	for emacs-devel@gnu.org; Wed, 10 Dec 2008 13:19:04 -0500
Original-Received: from [199.232.76.173] (port=46825 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LATeJ-0006PU-DC
	for emacs-devel@gnu.org; Wed, 10 Dec 2008 13:19:03 -0500
Original-Received: from fencepost.gnu.org ([140.186.70.10]:54652)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <rms@gnu.org>) id 1LATeJ-0003Q5-3T
	for emacs-devel@gnu.org; Wed, 10 Dec 2008 13:19:03 -0500
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.67)
	(envelope-from <rms@gnu.org>)
	id 1LATdi-00058t-LX; Wed, 10 Dec 2008 13:18:26 -0500
In-reply-to: <87myf5p3ki.fsf@master.homenet> (message from Giuseppe Scrivano
	on Tue, 09 Dec 2008 20:10:37 +0100)
X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6,
	seldom 2.4 (older, 4)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Xref: news.gmane.org gmane.emacs.devel:106764
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/106764>

    For example, we can't switch threads while they are executing:

    (setq a-global-variable (foo a-global-variable))

In most cases, there is no problem, because the code in the other thread
won't change this global variable.

I think it is better to have a variable `inhibit-thread-switch'
which you could bind around such sections when there is really an issue.