From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: emacs-dynamic-module in Emacs Git? Date: Mon, 01 Dec 2014 16:42:07 -0600 Message-ID: <85a937m1q8.fsf@stephe-leake.org> 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1417473765 5708 80.91.229.3 (1 Dec 2014 22:42:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Dec 2014 22:42:45 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 01 23:42:38 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 1XvZfv-0001WE-Cd for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 23:42:35 +0100 Original-Received: from localhost ([::1]:34257 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvZfv-0000Qn-23 for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 17:42:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38931) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvZfd-0000QW-0D for emacs-devel@gnu.org; Mon, 01 Dec 2014 17:42:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XvZfX-0001zs-So for emacs-devel@gnu.org; Mon, 01 Dec 2014 17:42:16 -0500 Original-Received: from dnvrco-outbound-snat.email.rr.com ([107.14.73.229]:30247 helo=dnvrco-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvZfX-0001zL-OK for emacs-devel@gnu.org; Mon, 01 Dec 2014 17:42:11 -0500 Original-Received: from [70.94.38.149] ([70.94.38.149:49722] helo=TAKVER) by dnvrco-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 78/94-24298-0CEEC745; Mon, 01 Dec 2014 22:42:08 +0000 In-Reply-To: (Ted Zlatanov's message of "Mon, 01 Dec 2014 10:36:10 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (windows-nt) X-RR-Connecting-IP: 107.14.64.142:25 X-Authority-Analysis: v=2.1 cv=F8jZd8RN c=1 sm=1 tr=0 a=AppmJ/7ZOOFWL/q6u6u93g==:117 a=AppmJ/7ZOOFWL/q6u6u93g==:17 a=ayC55rCoAAAA:8 a=fNEgcOh0sVsA:10 a=9i_RQKNPAAAA:8 a=f11AndE4AAAA:8 a=Rvp0wAaTG7j3_1TaJi0A:9 X-Cloudmark-Score: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 107.14.73.229 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:178658 Archived-At: Ted Zlatanov writes: > 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. In my particular case, this will not be useful; I need to call some ada-mode elisp functions from a compiled parser. These elisp functions will not be in any .h file, but I will need the appropriate "funcall" in that .h file. > 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 suggest waiting until a couple more people write actual modules. -- -- Stephe