Neil Nelson <n_nelson@pacbell.net> writes:
> Many thanks to John Williams for providing this solution.
>
> This solution has allowed me to compile .lisp programs,
> and at the moment that is sufficient. However I ran
> across a .lsp program from clx that was being compiled
> from a .lisp program which then failed (I just copied to
> .lisp for an interim solution). I expect it would be
> good to have a solution that will accept either extension.
>
> Regards,
>
> Neil Nelson
>
>
> johnw@cogs.susx.ac.uk wrote:
>
> >> I have been working on the following problem for awhile
> >> which is that load is looking for files with .lsp
> >> extension. The package I want to compile uses .lisp
> >> extensions.
> >
> >
> > LOAD merges the filename string with the path name
> > *DEFAULT-PATHNAME-DEFAULTS*. So if your filename doesn't contain
> > a type, it will have the type component of *DEFAULT-PATHNAME-DEFAULTS*
> > added, which is ".lsp".
> >
> > The solution is to put in your "init.lsp" file:
> >
> > (setq *default-pathname-defaults* #P"temp.lisp")
I would do
(setf (pathname-type *default-pathname-defaults*) "lisp")
In this way you are sure not to change the other default pathname
components.
--
Marco Antoniotti ========================================================
NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488
719 Broadway 12th Floor fax +1 - 212 - 995 4122
New York, NY 10003, USA http://bioinformatics.cat.nyu.edu
"Hello New York! We'll do what we can!"
Bill Murray in `Ghostbusters'.
|