Re: [armedbear-devel] compiling lisp files outside Java and calling it after with abcl

Hi,

Thanks for your help.

Because I've a lot of problems of java memory and Truncated class files, my intention is try to compile in the same platform with ABCL, but only compile, not to load from ABCL a file and then compile all files. If there are some way to compile all files with abcl and package... (I don't know if exists).

I see this web page and looks like, that you can load your fasl files (compiled abcl lisp files) from a jar file and then use it from Java, but I don't know who use it:

http://abcl-dev.blogspot.com/2009/09/loading-fasls-from-jar-files.html

Thanks

-----Mensaje original----- De: Alessio Stalla [mailto:alessiostalla@gmail.com] Enviado el: martes, 28 de febrero de 2012 13:59 Para: scarbonell@ono.com CC: armedbear-devel@common-lisp.net Asunto: Re: [armedbear-devel] compiling lisp files outside Java and calling it after with abcl

On Tue, Feb 28, 2012 at 12:32 PM, scarbonell@ono.com scarbonell@ono.com wrote:

Hi,

I'm trying to compile a lisp application and I get a lot of errors with

java

abcl. I thought that if I try to compile this lisp files outside of abcl with other systems, perhaps, I could then call this compiled functions

lisp

files from ABCL (look like a jar file of lisp compiled files). Is this possible?

How can I compiled this files outside ABCL? Some examples?

You can't do such a thing. Compiled Lisp code is implementation dependent. In general, you can not even be sure that two different versions of the same implementation, or the same version on different platforms, will be able to execute each other's compiled code.

For ABCL specifically, FASLs (compiled files) are portable across platforms, and are generally compatible with several versions of ABCL unless something big changed in the compiler between those versions (in that case, the FASL version number is changed, too).

Cheers, Alessio