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: DSO-style FFI Date: Wed, 09 Oct 2013 18:26:56 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87bo2yt70v.fsf@flea.lifelogs.com> References: <877gdqrc9u.fsf@flea.lifelogs.com> <87mwmmp05f.fsf@flea.lifelogs.com> <87fvsdpato.fsf@flea.lifelogs.com> <8738oc20xk.fsf@flea.lifelogs.com> <87d2ngzlyl.fsf_-_@flea.lifelogs.com> <87siwcxda7.fsf@flea.lifelogs.com> <87zjqjfz36.fsf@fleche.redhat.com> <87wqlnv9bn.fsf@flea.lifelogs.com> <52546F55.1020707@lanl.gov> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1381357626 20364 80.91.229.3 (9 Oct 2013 22:27:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Oct 2013 22:27:06 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 10 00:27:10 2013 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 1VU2Dl-0001xC-Kl for ged-emacs-devel@m.gmane.org; Thu, 10 Oct 2013 00:27:09 +0200 Original-Received: from localhost ([::1]:44151 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VU2Dl-0001HV-4J for ged-emacs-devel@m.gmane.org; Wed, 09 Oct 2013 18:27:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46145) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VU2Dc-0001HO-Rq for emacs-devel@gnu.org; Wed, 09 Oct 2013 18:27:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VU2DW-000223-SM for emacs-devel@gnu.org; Wed, 09 Oct 2013 18:27:00 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:60267) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VU2DW-00021v-LL for emacs-devel@gnu.org; Wed, 09 Oct 2013 18:26:54 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VU2DU-0001nX-LQ for emacs-devel@gnu.org; Thu, 10 Oct 2013 00:26:52 +0200 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Oct 2013 00:26:52 +0200 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Oct 2013 00:26:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 16 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net 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.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:tiCWRdW8q1nw1yiODVSHmcxbe8I= 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:164049 Archived-At: On Tue, 08 Oct 2013 14:47:17 -0600 Davis Herring wrote: DH> An interface like ctypes from Python would not involve Lisp_Objects on DH> the other side, but would rather provide a means for a Lisp program to DH> specify a mapping from its objects (Lisp_Objects, of course) to the C DH> datatypes appropriate to the interface. Simple things like "expose my DH> string as a writable char*" and "copy my integer into an int passed by DH> value" would suffice for many clients (or many target libraries, which DH> is much the same thing). libffi helps to formulate the actual calls DH> (with all their platform/ABI-dependent nonsense) based on such abstract DH> descriptions. That's pretty dangerous, isn't it? Any memory corruption, intentional or not, could affect the user significantly. Is that an acceptable risk? Ted