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: Dynamic loading progress Date: Mon, 28 Sep 2015 10:57:01 -0500 Message-ID: <86lhbq7d0y.fsf@stephe-leake.org> References: <55F5DD8C.70506@dancol.org> <55F62C16.4000105@dancol.org> <55F64F04.9030002@dancol.org> <55F6E43E.9030502@dancol.org> <55F70C4E.8030805@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1443487151 7527 80.91.229.3 (29 Sep 2015 00:39:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Sep 2015 00:39:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 29 02:39:00 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 1Zgiwd-0000k4-Ec for ged-emacs-devel@m.gmane.org; Tue, 29 Sep 2015 02:38:59 +0200 Original-Received: from localhost ([::1]:43032 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zgiwc-0000Z0-9v for ged-emacs-devel@m.gmane.org; Mon, 28 Sep 2015 20:38:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zgao5-0007gw-G2 for emacs-devel@gnu.org; Mon, 28 Sep 2015 11:57:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zgao2-0008MK-95 for emacs-devel@gnu.org; Mon, 28 Sep 2015 11:57:37 -0400 Original-Received: from gproxy9-pub.mail.unifiedlayer.com ([69.89.20.122]:38789) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Zgao2-0008LM-2O for emacs-devel@gnu.org; Mon, 28 Sep 2015 11:57:34 -0400 Original-Received: (qmail 25055 invoked by uid 0); 28 Sep 2015 15:57:23 -0000 Original-Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy9.mail.unifiedlayer.com with SMTP; 28 Sep 2015 15:57:23 -0000 Original-Received: from host114.hostmonster.com ([74.220.207.114]) by cmgw2 with id Nfx91r00h2UdiVW01fxCBL; Mon, 28 Sep 2015 09:57:21 -0600 X-Authority-Analysis: v=2.1 cv=Jv9i8qIC c=1 sm=1 tr=0 a=CQdxDb2CKd3SRg4I0/XZPQ==:117 a=CQdxDb2CKd3SRg4I0/XZPQ==:17 a=DsvgjBjRAAAA:8 a=f5113yIGAAAA:8 a=9i_RQKNPAAAA:8 a=hEr_IkYJT6EA:10 a=x_XPkuGwIRMA:10 a=ff-B7xzCdYMA:10 a=hEVegcIDr0efwaE7YDMA:9 Original-Received: from [76.218.37.33] (port=63133 helo=TAKVER2) by host114.hostmonster.com with esmtpa (Exim 4.84) (envelope-from ) id 1Zgane-0004Hj-Rr for emacs-devel@gnu.org; Mon, 28 Sep 2015 09:57:11 -0600 In-Reply-To: (Stefan Monnier's message of "Sun, 27 Sep 2015 23:01:02 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (windows-nt) X-Identified-User: {2442:host114.hostmonster.com:stephele:stephe-leake.org} {sentby:smtp auth 76.218.37.33 authed with stephen_leake@stephe-leake.org} X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 69.89.20.122 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:190449 Archived-At: Stefan Monnier writes: >> * pick a new syntax and teach make-docfile how to parse it. This is >> the clean approach IMO, but it requires more work. We can use a >> sufficiently simple syntax so that it can be embedded in comments in >> other languages than C. >> * define DEFVAR/DEFUN macro in module API header file to a noop so >> that make-docfile can parse it as it is. > > You're talking about how to get docstrings from the source code, but > I think we should expect Emacs to need/fetch them during "load" at which > point we'll be looking at the compiled code. So the first question is > where should those docstrings (regardless of whether they were found and > prepared by make-docfile or by some new tool) be located? Inside the > .so file? Is the source code which should be placed nearby? In some > kind of separate DOC file? At one point, we agreed that the module C code doc strings only need to be accessible after the module is loaded. That can be done with a function call in the module initialize function, along with the defun call. In that case, the doc strings are in the .so file. If the module author wants some doc strings to be accessible before load time, they can be on autoloaded functions in elisp code. -- -- Stephe