Embeddable Common-Lisp main repository.
Find a file
Daniel Kochmański 850f1ccce4 ffi: remove package nickname 'uffi'
Our ffi isn't uffi 2.0 compatible and most systems wants this, when
they say (require 'uffi). Also if system has asdf dependency on
quicklisp) we have package name error.

We'll depend with UFFI 2.0 compability on cffi-uffi-compat, what is
the saniest approach. Some ECL specific patches will land there soon
to improve performance - no internal FFI api will change. It's just
nick removal.

Signed-off-by: Daniel Kochmański <daniel@turtleware.eu>
2015-08-04 12:22:02 +02:00
contrib ffi: remove package nickname 'uffi' 2015-08-04 12:22:02 +02:00
examples An example on how to embed ECL using C compilers and ASDF. 2013-05-28 23:07:05 +02:00
msvc bdwgc: Update library to version 7.4.2. 2015-04-24 23:28:24 +02:00
src ffi: remove package nickname 'uffi' 2015-08-04 12:22:02 +02:00
.gitignore gitignore: ignore tgz archives. 2015-03-14 19:16:05 +01:00
CHANGELOG changelog: update on common changes 2015-08-03 16:11:52 +02:00
configure Preserve quoting when passing the arguments to the build directory 2008-08-27 09:50:44 +02:00
Copyright Release: update ANNOUNCEMENT and update Copyrights. 2015-02-21 20:35:51 +01:00
INSTALL New file with a sketch of the installation instrucitons 2009-08-12 23:54:41 +02:00
LGPL Initial revision 2001-06-26 17:14:44 +00:00
Makefile.in Makefile.in: slight cleanup 2015-06-19 13:05:00 +02:00
README README: change filename 2015-07-19 19:10:43 +02:00

You can find the preprocessed documentation in ./doc in HTML format.

Debugging via GDB:
------------------

src/util/gdbinit (and, therefore, build/.gdbinit) defines
a few convenience things - T, NIL, and, even more important,
ecl_print.

This is a GDB function that prints a 'cl_object' human-readably:

    (gdb) ecl_print x
    $39 = t_fixnum
    $40 = (ecl_base_char *) 0x42b4000 "10652336"

And another that helps to see a thread state:

    (gdb) ecl_eval "cl:*package*"

Please note that double quotes have to be escaped:

    (gdb) ecl_eval "(concatenate 'string \"a\" \"b\")"

Both will give a string with "readable" content, and a pretty-printed one.



Using VIM:
----------

.git/tags is a VIM-compatible tag file; if you're using
the fugitive plugin, it will be used automatically.



About testing:
--------------

make check
	to (get, initialize and) run the tests

make -C build/tests do-regressions
make -C build/tests do-ansi
make -C build/tests do-quicklisp
make -C build/tests do-mop-tests
	runs the specified tests

make -C build/tests/ show-fails
	prints results