On Wed, 08/11/06, Robert Dodier wrote:
> Leo,
>
>> Try this:
>> go_lisp()
>> (cmd)
>>
>> cmd is any non existing commands.
>
> I don't see the same behavior as you -- when I enter something like
> (sdkdkfsd), I get
>
> Maxima encountered a Lisp error:
> Error during processing of --eval option "(cl-user::run)":
> The function SDKDKFSD is undefined.
> Automatically continuing.
> MAXIMA>
>
> build_info() =>
> Maxima version: 5.10.0cvs
> Maxima build date: 7:55 11/1/2006
> host type: i686-redhat-linux-gnu
> lisp-implementation-type: SBCL
> lisp-implementation-version: 0.9.16
>
> I'm not sure how hard we should try to resolve this;
> it doesn't appear to be a Maxima bug, and it is only
> moderately annoying, at worst. But feel free to look into
> it if you have the time.
>
> What happens in sbcl by itself if you try to call an
> undefined function?
It enters something like this:
,----
| * (dkdk)
| ; in: LAMBDA NIL
| ; (DKDK)
| ;
| ; caught STYLE-WARNING:
| ; undefined function: DKDK
|
| ;
| ; caught STYLE-WARNING:
| ; This function is undefined:
| ; DKDK
| ;
| ; compilation unit finished
| ; caught 2 STYLE-WARNING conditions
|
| debugger invoked on a UNDEFINED-FUNCTION in thread #<THREAD "initial thread" {A68F5A1}>:
| The function DKDK is undefined.
|
| Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
|
| restarts (invokable by number or by possibly-abbreviated name):
| 0: [ABORT] Exit debugger, returning to top level.
|
| ("bogus stack frame")
| 0]
|
`----
>
> All the best,
> Robert Dodier
Thank you Robert. I have also reported this to bugzilla of Fedora core
5.
--
Leo