From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Patch for fields of `struct buffer' Date: Mon, 31 Jan 2011 15:00:47 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1296505847 19888 80.91.229.12 (31 Jan 2011 20:30:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 31 Jan 2011 20:30:47 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: Tom Tromey Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 31 21:30:42 2011 Return-path: 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.69) (envelope-from ) id 1Pk0OR-0004Nh-TR for ged-emacs-devel@m.gmane.org; Mon, 31 Jan 2011 21:30:36 +0100 Original-Received: from localhost ([127.0.0.1]:46250 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pk03D-0005Wx-7E for ged-emacs-devel@m.gmane.org; Mon, 31 Jan 2011 15:08:39 -0500 Original-Received: from [140.186.70.92] (port=35883 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pjzvj-00006y-K2 for emacs-devel@gnu.org; Mon, 31 Jan 2011 15:01:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pjzvd-000206-BT for emacs-devel@gnu.org; Mon, 31 Jan 2011 15:00:55 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:1705 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pjzvd-0001zu-8q; Mon, 31 Jan 2011 15:00:49 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEACejRk1MCpTp/2dsb2JhbACkeHS+DYVOBIUTj2g X-IronPort-AV: E=Sophos;i="4.60,405,1291611600"; d="scan'208";a="89979480" Original-Received: from 76-10-148-233.dsl.teksavvy.com (HELO ceviche.home) ([76.10.148.233]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 31 Jan 2011 15:00:48 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id E47BE660DC; Mon, 31 Jan 2011 15:00:47 -0500 (EST) In-Reply-To: (Tom Tromey's message of "Mon, 31 Jan 2011 08:30:14 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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:135348 Archived-At: > I will probably keep the current approach (the above shows "1"), since > the hair is all isolated in the thread-creation function, and since this > is how I expected it to work in the first place. BTW, I think the option 1 of sharing between threads might lead to complications in some implementations, since we now have variables which are neither global nor specific to a single thread but are shared by some subset of all threads. If those vars are never `setq'd, it's OK because this sharing can be eliminated by copying their values, but since we don't have such guarantees, it sounds like option 2 of "no sharing" is more future-proof. We can provide ways to transfer the value (but just the value) of some variables from a parent to his child. Stefan