Re: [clisp-list] compile-file merging source pathname with .lisp

[<fa...@gm...>]

Thanks a lot! By setting it CUSTOM:*SOURCE-FILE-TYPES* to nil, I can
happily compile cl-launch scripts. Will be in cl-launch 1.91.

NB: not an issue in cl-launch 1.90 when either dump images or having
scripts with an extension in name -- my regression test suite didn't
find it because it creates scripts with names in .sh.

[ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.tu=
nes.org ]
-- Question authority!
-- Yeah, says who?


On 09/10/06, Sam Steingold <sd...@gn...> wrote:
> Far=E9 wrote:
> > When I switched cl-launch to compile the current script, and tried to
> > create cl-launch scripts that didn't have a .sh extension, I realized
> > that clisp systematically merge-pathnames any provided source pathname
> > to add the type "lisp". This means that it's impossible to
> > compile-file a source file that doesn't have an extension at all
> > (unless you symlink it with another name).
> >
> > I think this is a bug that goes against the specification.
> > Automatically adding ".lisp" shouldn't be done at all, at least, not
> > if a file already exists without this extension.
>
> see CUSTOM:*SOURCE-FILE-TYPES*
> http://clisp.cons.org/impnotes/system-dict.html#compilefile
> http://clisp.cons.org/impnotes/system-dict.html#loadfile