[Gsll-devel] gsll:+edom+ has no value

[Liam Healy]

This shows up in the Debian version of CLISP, 2.44.1 as
well.  It appears to be a bug in CLISP.  If I replace the
first form in conditions.lisp (which creates the
defconstants) with the literal defconstants, it still gets
this error.  I think that a defconstant must be useable
immediately after it is defined, even in the same file.

If you are on the CLISP mailing list, can you post a
question there and confirm this?

Liam


On Fri, Jun 12, 2009 at 8:49 PM, Mirko Vukovic<mirko.vukovic at gmail.com> wrote:
> Hello,
>
> on loading a fresh gsll (no fasl, lib, exe) on clisp+cygwin+windows, I get:
>
> #<ADDRESS #x44C9D500>: variable GSLL::+EDOM+ has no value
>   [Condition of type SYSTEM::SIMPLE-UNBOUND-VARIABLE]
>
> Restarts:
>  0: [USE-VALUE] You may input a value to be used instead of GSLL::+EDOM+.
>  1: [STORE-VALUE] You may input a new value for GSLL::+EDOM+.
>  2: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL #x1018B8A1> on
> #<ASDF:CL-SOURCE-FILE "conditions" #x10465C61>.
>  3: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL #x1018B8A1> on
> #<ASDF:CL-SOURCE-FILE "conditions" #x10465C61> as having been
> successful.
>  4: [ABORT] Return to SLIME's top level.
>  5: [ABORT] Abort
>  --more--
>
> The call stack seems to originate in the `define-gsl-condition' (see
> attached file)
>
> Any ideas?
>
> Thanks,
>
> Mirko
>
> PS BTW, I had to teach cffi-grovel how to access gcc under cygwin.  I
> posted a message to cffi-grovel, so hopefully you will not need to do
> anything on the gsll side
>
> _______________________________________________
> Gsll-devel mailing list
> Gsll-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/gsll-devel
>
>