From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: emacs-dynamic-module in Emacs Git? Date: Mon, 01 Dec 2014 10:36:10 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: References: <87k32sh50f.fsf@lifelogs.com> <85tx1rg64e.fsf_-_@stephe-leake.org> <87siha7r3b.fsf@lifelogs.com> <87lhmz4mtj.fsf@lifelogs.com> <87sih575rc.fsf@lifelogs.com> <8361dyaqf1.fsf@gnu.org> <837fycae5p.fsf@gnu.org> <87y4qs19mi.fsf@lifelogs.com> <874mtfu0et.fsf@lifelogs.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1417448207 30121 80.91.229.3 (1 Dec 2014 15:36:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Dec 2014 15:36:47 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 01 16:36:40 2014 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 1XvT1j-0005eV-6I for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 16:36:39 +0100 Original-Received: from localhost ([::1]:60620 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvT1i-0001BC-OM for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 10:36:38 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvT1Z-00014D-8L for emacs-devel@gnu.org; Mon, 01 Dec 2014 10:36:35 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XvT1S-0005Qs-0q for emacs-devel@gnu.org; Mon, 01 Dec 2014 10:36:29 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:33069) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvT1R-0005Qo-RW for emacs-devel@gnu.org; Mon, 01 Dec 2014 10:36:21 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XvT1Q-0005U9-S2 for emacs-devel@gnu.org; Mon, 01 Dec 2014 16:36:20 +0100 Original-Received: from 198.0.146.153 ([198.0.146.153]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Dec 2014 16:36:20 +0100 Original-Received: from tzz by 198.0.146.153 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Dec 2014 16:36:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 19 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 198.0.146.153 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (darwin) Cancel-Lock: sha1:oDEgQN0qsXRUXvP0mxXLiWksVXI= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:178582 Archived-At: On Mon, 01 Dec 2014 10:04:34 -0500 Stefan Monnier wrote: SM> By "API" I meant something like a .h file which modules can include to SM> define the functions and datatypes that they can use. I.e. by API SM> I mean those things that the module code can do, rather than the things SM> that Emacs code can do with modules. By API I meant both directions, the module API for registration and metadata, and the Emacs API that modules can use. So I still think a call-only API (only in the direction of calling the module) is best for now, so that .h file is unnecessary. I agree with the rest of your comments, except that it's not clear when you'll feel that the module loading is settled enough to merge into the master branch. I think the module metadata should be formalized, at least, so it can be obtained before loading the module. Aurélien, is that possible? And do you have any comments? Ted