[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] Segmentation violation: c stack ok:signalling error with

From: Gabriel Dos Reis
Subject: Re: [Gcl-devel] Segmentation violation: c stack ok:signalling error with GCL-2.7.0 (cvs head)
Date: 29 Nov 2006 18:18:03 +0100

Camm Maguire <address@hidden> writes:

| Greetings!  You are missing the dsetq macro definition, found in
| vmlisp.lisp, and used here for example in your file:
| (DEFUN |centerNoHighlight| (&REST #1=#:G4770 &AUX |argList| |text|) 
|        (DSETQ (|text| . |argList|) #1#) (|sayBrightly| (|center| |text| 
| If dsetq is assumed a function, as is the default, this will not
| compile.  With the definition, it compiles fine.
| In general, the lisp produced by axiom will need some work to conform
| to ansi package semantics, if this is ever desired.  In particular,
| one needs to insure that the symbol vmlisp::dsetq and boot::dsetq are
| the same.  Here is one way:
| (make-package "VMLISP" :use '(lisp))
| (make-package "BOOT" :use '(lisp vmlisp))
| (load "vmlisp.lisp")
| (in-package 'vmlisp)
| (export '(dsetq))
| (in-package 'user)
| (compile-file "msgdb.lsp")
| With the cltl1 semantics, one can skip the extra make-package and do
| similar with only in-package.
| There are also many references to global variables.  If these are
| defvar'ed elsewhere, including this file too before compilation will
| reduce the warnings.

Dear Camm, thank you very much for looking into this.
vmlisp.lisp has become a kind of black hole attracting all kinds of

We will make sure that that black hole stops growing, and in
particular there is only one symbol, dsetq and it is defined.

Yes, many people have suggested that it would be a good idea for Axiom
to move to ANSI semantics.


-- Gaby

reply via email to

[Prev in Thread] Current Thread [Next in Thread]