mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-05-01 12:20:26 +02:00
66ff15e2f0
* module/Makefile.am: Add language/sassy.scm. Probably EXTRA_DIST the dependant files, too. * module/language/sassy.scm: New file, the sassy loader. Sassy is originally R5RS code that loads a number of files. I've converted that toplevel file to be a Guile module that *includes* the subfiles, so that it all gets compiled together. It's a pretty bad hack though, because what I should be doing is including them relative to the sassy.scm source location, but we don't know that at expansion time. Something to fix. really bad hack in it so that it will compile correctly -- p * module/language/sassy/: All the sassy files and some changelog information. All of these files are LGPLv2.1+, so they can be included in Guile. * test-suite/standalone/sassy/tests/: Add the sassy unit tests. * test-suite/standalone/Makefile.am: * test-suite/standalone/test-sassy: Hook the sassy unit tests up to our test suite. |
||
|---|---|---|
| .. | ||
| sassy/tests | ||
| .gitignore | ||
| Makefile.am | ||
| README | ||
| test-asmobs | ||
| test-asmobs-lib.c | ||
| test-bad-identifiers | ||
| test-conversion.c | ||
| test-extensions | ||
| test-extensions-lib.c | ||
| test-fast-slot-ref.in | ||
| test-list.c | ||
| test-num2integral.c | ||
| test-require-extension | ||
| test-round.c | ||
| test-sassy | ||
| test-scm-c-read.c | ||
| test-scm-take-locale-symbol.c | ||
| test-scm-with-guile.c | ||
| test-system-cmds | ||
| test-unwind.c | ||
| test-use-srfi.in | ||
| test-with-guile-module.c | ||
-*-text-*- These tests use the standard automake TESTS mechanism. Tests should be listed in TESTS in Makefile.am, and should exit with 0 on success, non-zero on failure, and 77 if the result should be ignored. See the automake info pages for more information. If you want to use a scheme script, prefix it as follows: #!/bin/sh exec guile -s "$0" "$@" !# Makefile.am will arrange for all tests (scripts or executables) to be run under uninstalled-env so that the PATH, LD_LIBRARY_PATH, and GUILE_LOAD_PATH will be augmented appropriately. The Makefile.am has an example of creating a shared library to be used from a test scheme script as well. You can also create standalone executables that include your own code, are linked against libguile, and that run a given test script (or scripts). One way to do this is to create the binary, make sure it calls scm_shell (argc, argv) as its final action, and put this bit at the top of your test script: #!./my-test-binary -s !#