>>> Second: sbcl and especially ecl like it much better if you compile the lsp >>> files generated with the aldor compiler >> What does that mean? > > ecl complains about "too large jump" in aldor-combinat, unless you compile the > files. sbcl is *much* faster on compiled files.
Does that just mean that instead of for f in $(ar t libcombinatax.al); do echo ")lib $f" >> combinat.input; done we should have something like for f in $(ar t libcombinatax.al); do n=$(basename $f .ao); echo ")compile $n.lsp" >> combinat.input; echo ")lib $n" >> combinat.input; done in Aldor-combinat? Ralf ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Aldor-combinat-devel mailing list Aldor-combinat-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aldor-combinat-devel