Steel Bank Common Lisp

Windows .FASL extension should force LOAD to treat as fasl file

Reported by Willem Broekema on 2009-11-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Medium
Unassigned

Bug Description

This is about how SBCL deals with invalid fasl files, like fasl files from other implementations.

On Windows, (load "foo.fasl") will load the file as fasl file, and signal FASL-HEADER-MISSING if the header is invalid. OK.

But loading the same file as (load "foo.FASL") will treat invalid an fasl as source code, which leads to somewhat strange errors (e.g. UNBOUND-VARIABLE of a variable whose name contains unprintable bytes).

As nobody would give a source file the extension FASL, I propose that the test for the "fasl" extension is done on Windows with string-equals instead of string= (function load, in src/code/target-load.lisp).

 status fixcommitted
 importance medium

In 1.0.33.24, thanks for the report!

Changed in sbcl:
importance: Undecided → Medium
status: New → Fix Committed
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers