Source ffidl-full.tar.gz ffidl.tar.gz Windows Binary Ffidl0.6.zip MacOSX Binary Ffidl-0.6.tar.bz2 Ffidl.pkg.tar.bz2 Commands, et al. ::ffidl::callout ::ffidl::callback ::ffidl::symbol ::ffidl::stubsymbol ::ffidl::typedef ::ffidl::info ffidl_pointer_pun ::ffidl::find-lib ::ffidl::find-type Types Install Demos Performance Issues Credits ::dll libffi ffcall ffidl-0.6 Copyright License No Warranty | Ffidl Version 0.6 Ffidl-0.5, 6 years after its release, was graciously updated by Daniel A. Steffen, tested on a barrage of systems, and released as Ffidl-0.6. I incorporate his description of his work and update to my work here, and link copies of his release sources and binaries. The ffidl-0.5 index is here. Ffidl allows you to call C functions using pure Tcl wrappers. You specify a function name, a library, a list of argument types, and a return type, and Ffidl takes care of the nasty details of converting a Tcl command call into a C function call for you. So, if you have a shared library and a specification of the entries in the library, you can wrap the library into a Tcl extension with Ffidl and pure Tcl. Ffidl 0.6 has the following changes since 0.5:
The 0.6 changes were implemented by Daniel A. Steffen and are under BSD License; do not contact the original Ffidl author for support about them. Ffidl 0.6 has been verified to build and pass its testsuite on the following platforms:
Ffidl uses the latest libffi-2.00-beta from gcc CVS to dynamically construct calls to C functions from Tcl, to dynamically construct calls from C functions into Tcl. gcc libffi runs on all platforms where gcj is available (which uses it). Ffidl can also be configured (--enable-ffcall) to use ffcall-1.10 a GPL'ed foreign function package which implements both callouts and callbacks on:
Ffidl uses Tcl's TclpDlopen() and TclpFindSymbol(), to load dynamic libraries and discover the locations of functions. Ffidl should be able to run on any system with a stubs enabled Tcl, libffi or ffcall support, and a libdl implementation. Ffidl 0.6 is an alpha release. There are configuration details which you will need to attend to by hand in the current release. The initial development turned up a few bugs in libffi under linux-x86, so users on other architectures should be alert for similar problems. There are several open design issues still to be resolved, so there may be changes in the interfaces in future releases. Assistance is needed to verify that the implementation works on all the architectures supported by libffi, and the open design issues could use some discussion. Commands, Functions, and Procs Ffidl defines six Tcl commands in the Ffidl package: ::ffidl::callout, ::ffidl::callback, ::ffidl::symbol, ::ffidl::stubsymbol, ::ffidl::typedef, and ::ffidl::info; exports one function from the Ffidl shared library: ffidl_pointer_pun; and defines two helper procs in the Ffidlrt package in demos/ffidlrt.tcl: ::ffidl::find-lib, and ::ffidl::find-type, which are currently just stubs of their true form. These interfaces should be considered subject to revision.
The Ffidl builtin types include the scalar C types in both their unsized forms and as explicitly bit sized types, and a variety of pointer treatments. Note that some types are only valid in certain contexts: arguments (arg), return (ret), or struct elements (elt). In addition to the builtin types, the ::ffidl::typedef command may be used to define new types. Aliases for existing types may be used where ever the existing type may be used. Structured aggregates may be used as arguments, returns, or elements of other structures.
Building on plaforms supported by TEA 3.2 should be painless. Installation is like for any other TEA extension, minimally it consists of: tar xzvf ffidl-full.tar.gz cd ffidl configure && make Custom configure options are implemented for selecting between libffi and ffcall (--enable-libffi and --enable-ffcall), for excluding callbacks (--disable-callbacks) and for enabling building of the ffidl test functions into the extension (--enable-test). On non-Darwin Unix and on Windows you should edit library/ffidlrt.tcl and look at the table of libraries in ::ffidlrt::libs and the table of types in ::ffidlrt::types. Either or both of these tables will probably need attention if you go further. You may need, for instance, to find, build, or install libraries for gmp and gdbm, or to adjust the pathnames for libc, libm, tcl, and tk. Running make testwill run the ffidl tests (when configured with --enable-test). It is not quite a systematic test suite, but it does exercise a good deal of Ffidl's capabilities, and it has turned up some problems with libffi. The demos directory contains several small and medium size examples of Ffidl bindings to shared libraries, and some code for making comparisons to other ways of doing the same thing.
library/ffidlrt.tcl will need attention unless you're running on Darwin. There are two functions, ::ffidl::find-lib and ::ffidl::find-type, which abstract library names and system typedefs out of the rest of the code. However, the abstraction on Unix is currently limited to the correct results for my Linux box. You'll need to rewrite the mapping for your own machine. ibrary/ffidlrt.tcl also contains some examples of binding into the Tcl core itself. demos/tkphoto.tcl allows extraction and insertion of photo image pixels as binary data. See tests/tkphoto.test for an example. The demos/other/gdbm.tcl extension should be plug compatible with Tclgdbm0.6, a C coded Tcl extension for manipulating gdbm files. Since gdbm passes and returns structures, it also tests the Ffidl struct code. The demos/other/gmp*.tcl extensions make a nice example. The main Gmp package wraps all the exported mpz_*, mpq_*, and mpf_* entries from the Gnu multiple precision library. The subsidiary Gmp[zqf] packages use the Gmp package to define arbitrary precision integers, rationals, and floats which are represented as strings. This isn't the most efficient way to do arbitrary precision arithmetic, but it is convenient, it does avoid needing to know what type mp_limb_t and mp_size_t actually are, and it does show how to use the underlying library if you want to build something more efficient. Performance appears to be excellent, but I can't take any credit because libffi is doing most of the work. The demos/mathswig/time-libm.tcl script compares ::ffidl::callout wrapped libm functions to the Tcl expr versions of the same functions. You'll need to manually build the libmathswig0.5 dynamic library to provide a SWIG wrapped libm for comparison purposes. If you're running on Linux-x86 or Windows you can install Robin Becker's ::dll for another data point. demos/mathswig/time-libm.tcl will time them on the same functions. A few issues have been closed since the initial release. The Windows port is done. Callbacks are implemented for the x86 architecture. But there are many open issues. Finding the right library is a pain. dlopen("libm.so") finds libm on my machine, but dlopen("libc.so") returns an error string decorated with binary characters while dlopen("libc.so.6") works. If you work with shared libraries you build yourself, it's not an issue, but for all the standard stuff there is no standard. In demos/ffidlrt.tcl the ::ffidl::find-lib function provides an abstraction for at least removing these issues one layer away from your Ffidl bindings to the library, but the implementation of the abstraction hasn't gone farther than listing where I find my standard libraries. Discovering what type a type is is also a pain. Include headers are typically so heavily conditionalized, that one needs to search and search to find which typedef is actually implemented. In demos/ffidlrt.tcl the ::ffidl::find-type function abstracts these issues out of the Ffidl bindings, but again the implementation of the abstraction will need some work. A backend for SWIG which generates Ffidl bindings might be useful. There are some more pointer types which ought to be defined: a variant of pointer-var which requires an unshared value; a pointer to a native character string -- but couldn't that be pushed back to the Tcl layer? Writing Tcl extensions with Ffidl is very much like writing C code in Tcl. I'm not sure what the actual required skill set is. But if you're not sure what you're doing, you might be in over your head. In any case, try not to take the core dumps personally. Loading snippets of code into a Tcl interpreter with Ffidl loaded could be very hazardous, as in downloading "Try ME!" scripts from the web. There is no Ffidl_SafeInit(), we'd probably need signed scripts to even begin to consider such a thing. I've looked at SWIG and at dll and seen that they very carefully duplicate any shared Tcl_Obj before attempting a conversion to Int or Double. I've also looked at the source for Tcl's expr command, and it converts objects to Double or Int and only duplicates shared objects when it finds a valid Int or a Double with an existing string representation. Ffidl only duplicates shared objects when processing pointer-var, though I'm open to explanations why it should do otherwise. It seems that if you pass a parameter to a typed function that you shouldn't be upset if the parameter is converted to that type. Hmm, this is a really pared to the bone. It would be nice for newbies and experimenters and the careless if Ffidl implemented a debugging mode which verified that constraints were observed: 1) that Tcl_Obj string reps were not modified, 2) that Tcl_Obj bytearray reps were not modified outside their allocated sizes, and so on. This could be done by switching in an alternate implementation of tcl_ffidl_call() which made copies and verified the constraints after the call. Some naming consistency in the demos. I seem to be reinventing my Ffidl extension style each time I start a new example. Some style consistency in the tests. The tests just run, some generate descriptions, some report what they've done, some say nothing, some give summaries. Robin Becker's ::dll package, which does much the same thing as Ffidl, provided the immediate inspiration for this work and pointed to the solution of some of the design issues for me. And Robin hisself has been very helpful. Anthony Green's libffi package provided most of the initial implementation of Ffidl. Bruno Haible's ffcall package for the clisp system provided an alternate implementation and a truly amazing example of cpp macrology. Copyright, License, & No Warranty Ffidl Version 0.6, Copyright © 1999 by Roger E Critchlow Jr, Santa Fe, NM, USA Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ``Software''), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL ROGER E CRITCHLOW JR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Changes from ffidl 0.5 are under BSD License and are Copyright © 2005 by Daniel A. Steffen Note that libffi is Copyright © 1996-2003 Red Hat, Inc. and bears a similar copyright notice, license, and non-warranty. Note that ffcall-1.10 is Copyright © 1995-2004 Bruno Haible, © 2000 Adam Fedor, © 2004 Paul Guyot and is licensed under the GNU General Public License .
|