Re: Is it possible to use custom extension of compiled files (Windows 64bit).
Martin Simmons <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
Yes, you can add it to system:*binary-file-types* https://www.lispworks.com/documentation/lw81/lw/lw-sys-12.htm#LWUGRM)*binary-file-types* -- Martin Simmons LispWorks Ltd http://www.lispworks.com/ >>>>> On Wed, 17 Sep 2025 17:36:50 +0000, Uģis Lācis (as ugis dot lacis at equa dot se) said: > > I am currently experimenting with compiling and loading my code in both SBCL and LispWorks on 64bit Windows. LispWorks behaves seemingly strange. I can get file to compile and load just fine as long as I use *.64ofasl extension. If I instead use :output-file option for compile-file function and use a custom extension (such as *.fsl or *.fasl), compilation executes without problems as previously, whereas loading fails with: > Error: Cannot read character Backspace as part of a token because it has constituent trait 'invalid'. > > It seems that the file gets treated as a text file instead. I have tried to look for any option to fix this (or any reference to the limitation) in documentation but have not found anything. SBCL does not seem to have this issue. > > I could, of course, move over to .64ofasl extension, but for historical reasons we compile files into *.fsl files and if there is something easy/obvious I am missing, it could be nice to stick with this. Does anyone have any comments on this? > > Best wishes, > Ugis > _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html