From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: FFI in Emacs Date: Wed, 11 Jul 2012 20:49:41 +0300 Message-ID: <83mx36b32i.fsf@gnu.org> References: <877gua6a6n.fsf@uwakimon.sk.tsukuba.ac.jp> <83vchub7m5.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: dough.gmane.org 1342029023 3548 80.91.229.3 (11 Jul 2012 17:50:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 11 Jul 2012 17:50:23 +0000 (UTC) Cc: johnw@newartisans.com, stephen@xemacs.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Samuel Bronson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 11 19:50:20 2012 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 1Sp13I-0005hW-UG for ged-emacs-devel@m.gmane.org; Wed, 11 Jul 2012 19:50:17 +0200 Original-Received: from localhost ([::1]:45343 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sp13I-0001PH-6A for ged-emacs-devel@m.gmane.org; Wed, 11 Jul 2012 13:50:16 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:47312) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sp13E-0001PB-Sy for emacs-devel@gnu.org; Wed, 11 Jul 2012 13:50:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sp13D-00025Y-Lo for emacs-devel@gnu.org; Wed, 11 Jul 2012 13:50:12 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:48346) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sp13D-00025I-Db for emacs-devel@gnu.org; Wed, 11 Jul 2012 13:50:11 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M7000600BENAY00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Wed, 11 Jul 2012 20:49:45 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.210.75]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M70005H0C6WVJC0@a-mtaout22.012.net.il>; Wed, 11 Jul 2012 20:49:44 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.172 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:151540 Archived-At: > Cc: "Stephen J. Turnbull" , > johnw@newartisans.com, > monnier@iro.umontreal.ca, > emacs-devel@gnu.org > From: Samuel Bronson > Date: Wed, 11 Jul 2012 13:08:33 -0400 > > > On Jul 11, 2012, at 12:11 PM, Eli Zaretskii wrote: > > >> From: "Stephen J. Turnbull" > >> Date: Wed, 11 Jul 2012 16:14:56 +0900 > >> Cc: Stefan Monnier , emacs-devel@gnu.org > >> > >> [SXEmacs FFI interface] should be fairly easily portable to Emacs on > >> platforms that have libffi. It probably doesn't work on Windows > > > > Why not? Not because of libffi, I think. libffi compiles out of the > > box with MinGW; I did that when I needed to build Guile on Windows, > > and my notes from that time indicate that the only libffi issue was a > > rather minor problem with "make install". And there are precompiled > > Windows binaries available on the net. > > > It's wise to assume that code that hasn't been tried on Windows > recently might need at least some porting, especially when it has > anything to do with dynamic loading or calling conventions. I see no need to assume anything when there are facts available. I revealed the facts known to me so that people won't need to assume. > Despite > all the things the NT hackers picked up from *nix, NT does many things > rather differently, including what they call DLLs, and the APIs for > loading them dynamically. AFAIK, libltdl is used for actually loading the modules. libltdl also works on Windows, with binaries readily available. So I really don't know what you are talking about.