Greetings, and thanks Waldek! Should be fixed now. (The format of
this report was very helpful.)
BTW, though sgc should be fine now, and it might be nice to confirm,
in general one should only put on sgc at the end of the axiom build
before saving the final image. SGC is a read-only memory bifu
Camm Maguire <[EMAIL PROTECTED]> writes:
> Greetings! Just interested, why do you execute si::top-level by hand?
Its just a hackish way of establishing bindings with dynamic extent
and quickly testing the effect on the system. Executing the )fin
command at axiom toplevel returns to enclosing li
Greetings! Just interested, why do you execute si::top-level by hand?
Take care,
Stephen Wilson <[EMAIL PROTECTED]> writes:
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
>
> > Later I hit problem with setting memory parameters, gcl complained:
> >
> > Condition in APPLY [or a callee]: INTERNAL
Greetings, and thanks again as always!
Waldek Hebisch <[EMAIL PROTECTED]> writes:
> I wrote:
> > > But later I hit another one: I am getting messages like:
> > >
> > > ;; Compiling stage0/ptyout.clisp.
> > > Segmentation violation: c stack ok:signalling errorError in error:
> > > ERROR TYPE-ERRO
Camm,
Thanks a lot for your work on GCL.
My only comment about recompiling policy is that I hope that
the system remains in a safe state by default.
About this,
A final question remains of
whether or not to actually use ftype declaims if provided.
My advice: ignore user-supplied ftype decla
Camm --
The info page for compiler::link lists the parameters
"raw" and "init" as &aux. However, my understanding is that
the implementation in both 2.6.8pre and 2.7.0 does not have them.
Did I misunderstand?
-- Gaby
___
Gcl-devel mailing list
Gcl
