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: Dynamic loading progress Date: Wed, 30 Sep 2015 04:52:30 -0400 Message-ID: References: <87si7977rs.fsf@tromey.com> <55DB7C3D.4090106@cs.ucla.edu> <55DE75FD.8020308@cs.ucla.edu> <55F5DD8C.70506@dancol.org> <87fv2hzmw3.fsf@uwakimon.sk.tsukuba.ac.jp> <22025.61338.681227.470671@turnbull.sk.tsukuba.ac.jp> <560AFCE3.8090802@lanl.gov> <22027.31797.6292.498407@turnbull.sk.tsukuba.ac.jp> <560B8EB9.8030801@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1443677273 9097 80.91.229.3 (1 Oct 2015 05:27:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Oct 2015 05:27:53 +0000 (UTC) Cc: Paul Eggert , Emacs development discussions , Philipp Stephani , =?windows-1252?Q?Aur=E9lien?= Aptel , "Stephen J. Turnbull" , Tom Tromey , Stephen Leake To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 01 07:27:43 2015 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 1ZhWP7-00027X-Uy for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2015 07:27:42 +0200 Original-Received: from localhost ([::1]:38277 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhWP7-0004t0-6j for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2015 01:27:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhD7r-000087-9x for emacs-devel@gnu.org; Wed, 30 Sep 2015 04:52:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZhD7o-0007yd-32 for emacs-devel@gnu.org; Wed, 30 Sep 2015 04:52:35 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:10738) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhD7n-0007yY-VQ for emacs-devel@gnu.org; Wed, 30 Sep 2015 04:52:32 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CXDQA731xV/wihxEVcgxCEAshgBAICgTw8EQEBAQEBAQGBCkEFg10BAQRWIxALDiYBERQYDSSIP88jAQEBAQYCAR+LOoUFB4QtBbM/gUUjhBQigngBAQE X-IPAS-Result: A0CXDQA731xV/wihxEVcgxCEAshgBAICgTw8EQEBAQEBAQGBCkEFg10BAQRWIxALDiYBERQYDSSIP88jAQEBAQYCAR+LOoUFB4QtBbM/gUUjhBQigngBAQE X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="166497852" Original-Received: from 69-196-161-8.dsl.teksavvy.com (HELO ceviche.home) ([69.196.161.8]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Sep 2015 04:52:31 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 038EF6624A; Wed, 30 Sep 2015 04:52:30 -0400 (EDT) In-Reply-To: <560B8EB9.8030801@dancol.org> (Daniel Colascione's message of "Wed, 30 Sep 2015 00:26:49 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.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.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:190506 Archived-At: BTW, all this discussion about C++ modules seems to miss the point: Emacs's own API will be a C API. When you want to use it from a C++ module, you'll have to convert it to a C++ API. At that point, you have various options: - do a minimalist binding which keeps using naked longjmp, and just let the C++ code use explicit internal_condition_case wrappers where it thinks it's needed. - do an "idiot-proof" binding which only provides a "safe_funcall" which catches longjmps and turns them into local exits. - do an "idiot-resistant" binding which only provides a "safe_funcall" that catches longjmps and turns them into C++ exceptions, and then back into Elisp longjmps (and back-and-forth ad nauseum if needed when doing nested mutual callbacks). - ...younameit... I'm fine with any of those things, and AFAIK they can all be done on top of the plain C API with the usual non-local exits. All I care about at this point is the plain C API. Stefan