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: [Emacs-diffs] /srv/bzr/emacs/trunk r109327: Generalize INTERNAL_FIELD between buffers, keyboards and frames. Date: Mon, 06 Aug 2012 12:31:50 -0400 Message-ID: References: <50191B54.2070705@yandex.ru> <5019FE2D.2060005@yandex.ru> <501B8C48.3000704@yandex.ru> <501C1F4D.5010007@cs.ucla.edu> <501D4E6F.6040702@cs.ucla.edu> <501E8B4B.3000805@yandex.ru> <501FAE02.80703@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1344270731 11924 80.91.229.3 (6 Aug 2012 16:32:11 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 6 Aug 2012 16:32:11 +0000 (UTC) Cc: Paul Eggert , emacs-devel@gnu.org To: Dmitry Antipov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 06 18:32:10 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SyQDv-0003vs-G9 for ged-emacs-devel@m.gmane.org; Mon, 06 Aug 2012 18:32:07 +0200 Original-Received: from localhost ([::1]:49283 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyQDu-0006j0-Ok for ged-emacs-devel@m.gmane.org; Mon, 06 Aug 2012 12:32:06 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:51053) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyQDn-0006in-1z for emacs-devel@gnu.org; Mon, 06 Aug 2012 12:32:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SyQDg-0005P0-Na for emacs-devel@gnu.org; Mon, 06 Aug 2012 12:31:58 -0400 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:60272) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyQDg-0005Os-Jo for emacs-devel@gnu.org; Mon, 06 Aug 2012 12:31:52 -0400 Original-Received: from faina.iro.umontreal.ca (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id q76GVobm015669; Mon, 6 Aug 2012 12:31:50 -0400 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id 92A44B41E3; Mon, 6 Aug 2012 12:31:50 -0400 (EDT) In-Reply-To: <501FAE02.80703@yandex.ru> (Dmitry Antipov's message of "Mon, 06 Aug 2012 15:44:02 +0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV4302=0 X-NAI-Spam-Version: 2.2.0.9309 : core <4302> : streams <795362> : uri <1185319> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:152225 Archived-At: >> I want the C part of Emacs to look like C code. So, if the >> structure-field access does not require extra machinery (i.e. no read >> barrier), I want to write it "foo->bar". > I (and I hope all others) too. But we do AREF and ASET for vectors, > thinking about that vector implementation may be changed so direct access > to 'contents' becomes invalid or nonsense. No, AREF is just convenience a macro (from where I stand), like XCAR/XCDR. > Development (and politics) is the art of the possible, and we have those > tools which are. I investigated this area, and I believe that coccinelle > is good enough to be used in our work; finally, I don't see the practical > reasons to wait until someone develops a wunderwaffe like GCC plugin > for automatic barrier insertion on any critical pointer stores. I'm not sure whether you're saying that Coccinelle is good enough to solve the problem I want solved (i.e. like me write "foo->bar" and turn it into "RVALUE_FIELD (foo, bar)" when I need to check correct insertion of write barriers). If it is, that's great. Stefan