From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Fri, 20 Nov 2015 20:00:25 +0000 Message-ID: References: <8737wgw7kf.fsf@lifelogs.com> <87io5bv1it.fsf@lifelogs.com> <87egfzuwca.fsf@lifelogs.com> <876118u6f2.fsf@lifelogs.com> <8737w3qero.fsf@lifelogs.com> <831tbn9g9j.fsf@gnu.org> <878u5upw7o.fsf@lifelogs.com> <83ziya8xph.fsf@gnu.org> <83y4du80xo.fsf@gnu.org> <564DF0F6.5060501@cs.ucla.edu> <564E5375.3050006@cs.ucla.edu> <564E6045.6030907@cs.ucla.edu> <8337w16kvs.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7bb04dc415aa550524fe5404 X-Trace: ger.gmane.org 1448049662 11402 80.91.229.3 (20 Nov 2015 20:01:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 20 Nov 2015 20:01:02 +0000 (UTC) Cc: aurelien.aptel+emacs@gmail.com, tzz@lifelogs.com, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 20 21:01:02 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 1ZzrrT-00039d-Jp for ged-emacs-devel@m.gmane.org; Fri, 20 Nov 2015 21:00:47 +0100 Original-Received: from localhost ([::1]:49629 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzrrT-0007f7-43 for ged-emacs-devel@m.gmane.org; Fri, 20 Nov 2015 15:00:47 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzrrK-0007ew-GC for emacs-devel@gnu.org; Fri, 20 Nov 2015 15:00:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzrrJ-0007qz-FG for emacs-devel@gnu.org; Fri, 20 Nov 2015 15:00:38 -0500 Original-Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:38162) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzrrH-0007qc-3z; Fri, 20 Nov 2015 15:00:35 -0500 Original-Received: by wmec201 with SMTP id c201so34865523wme.1; Fri, 20 Nov 2015 12:00:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=VW3T6xq7LZv98lBhMG8oVksPjUm7Cu7J88hPZYNFtJw=; b=UDsNot9CoAagj/WBdaH6IKCFjvyP1hxOAcWNGb8uX7Yey3b6d9lu6LVnGUhagOOPap A5d1QI0pbydxFxk8wBAhkMLE5X/OzmVCNKirjB8o7sE4w11TIW45/8KgKcaMJgrWFnxm XgjpkVwFufdefuCuWrtxOkbr3yHZNavp4ZpPs8NRcF2ctOANjSgm6wuIY6fAXdt4G0Oz QRMV/ceUSiQn5Ys2wN/MIRW1vlPalfpVhZIiLKuHlpMnRjXFPOtDSaPrsRy0QI3EEu5l XBwvPpcp2Yyy/abEUnulJMqHicAuQL0YKnYoG4LApRC1OE8BV5oEme0Kb87fHSIYT6rh xfPw== X-Received: by 10.195.13.135 with SMTP id ey7mr16190921wjd.25.1448049634550; Fri, 20 Nov 2015 12:00:34 -0800 (PST) In-Reply-To: <8337w16kvs.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c09::236 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:194891 Archived-At: --047d7bb04dc415aa550524fe5404 Content-Type: text/plain; charset=UTF-8 Eli Zaretskii schrieb am Fr., 20. Nov. 2015 um 11:11 Uhr: > > From: Philipp Stephani > > Date: Thu, 19 Nov 2015 23:55:57 +0000 > > Cc: emacs-devel@gnu.org > > > > Modules cannot (legally) call xmalloc. They need to obtain memory using > malloc > > or any other standard function. > > How is calling malloc different from calling xmalloc? Neither is in > the interface defined in emacs-module.h, right? > malloc is a standard C function, xmalloc is an internal Emacs function. > > > In general, modules cannot call any functions except those declared > > in emacs-module.h. > > Can they call functions from external libraries? (I thought allowing > that was one of the main design goals.) If so, what's the difference? > yes, sorry, I was being sloppy. Modules cannot call any Emacs C functions except those declared in emacs-module.h. Of course they can call arbitrary other library functions. --047d7bb04dc415aa550524fe5404 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Eli Za= retskii <eliz@gnu.org> schrieb am= Fr., 20. Nov. 2015 um 11:11=C2=A0Uhr:
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Thu, 19 Nov 2015 23:55:57 +0000
> Cc: emacs-dev= el@gnu.org
>
> Modules cannot (legally) call xmalloc. They need to obtain memory usin= g malloc
> or any other standard function.

How is calling malloc different from calling xmalloc?=C2=A0 Neither is in the interface defined in emacs-module.h, right?

malloc is a standard C function, xmalloc is an internal Emacs func= tion.
=C2=A0

> In general, modules cannot call any functions except those declared > in emacs-module.h.

Can they call functions from external libraries?=C2=A0 (I thought allowing<= br> that was one of the main design goals.)=C2=A0 If so, what's the differe= nce?

yes, sorry, I was being sloppy. Mo= dules cannot call any Emacs C functions except those declared in emacs-modu= le.h. Of course they can call arbitrary other library functions.
= =C2=A0
--047d7bb04dc415aa550524fe5404--