RE: [Gcl-devel] defpackage non-compliant?

[Mike Thomas]

Hi Sam.

| 3. There appears to be no way to tell GCL to compile "foo.lisp" on
|    (COMPILE-FILE "foo"); quits with "no foo.lsp" message.

I added yesterday two new functions COMPILER::COMPILER-DEFAULT-TYPE and
COMPILER::COMPILER-RESET-TYPE in CVS.  An extract from the doc follows my
"signature".

At the moment only one default ending is allowed to be set at any particular
point in time eg one only of ".lsp" or ".lisp" or ".something" or ".other",
but that can be changed if necessary.

Cheers

Mike Thomas.

========================================================================
COMPILER-DEFAULT-TYPE (pathname)  Function
Package:COMPILER
Allows you to set the default file extension for compiler source files. The
argument can either be a pathname or a string. For example, imagine you have
two files, "foo.lisp" and "foo1.lsp" in your working directory. (Note the
different extensions.) Then:


          >(compile-file "foo")

          The source file foo.lsp is not found.
          NIL

          >(compile-file "foo1")

          Compiling foo1.lsp.
          End of Pass 1.
          End of Pass 2.
          OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0,
Speed=3
          Finished compiling foo1.
          #p"foo1.o"

          >(compiler::compiler-default-type "lisp")

          #p".lisp"

          >(compile-file "foo")

          Compiling foo.lisp.
          End of Pass 1.
          End of Pass 2.
          OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0,
Speed=3
          Finished compiling foo.
          #p"foo.o"

          >(compile-file "foo1")

          The source file foo1.lisp is not found.
          NIL

          >





COMPILER-RESET-TYPE ()  Function
Package:COMPILER
Resets the default compiler input file extension to the GCL historical value
of #".lsp".

========================================================================