Greetings! These are what I have found -- light search only:
|initializeSetVariables|
|displaySetOptionInformation|
|displaySetVariableSettings|
|set1|
Take care,
d...@axiom-developer.org writes:
> Camm,
>
> What function in Axiom relies on this? I will fix it.
>
> Tim
>
>
>
>
--
Camm Magui
Camm,
This is due to an unfortunate name ambiguity. There is a
|functionp| function (axiom) and a functionp function (lisp).
I renamed |functionp| to canFuncall? which removed the ambiguity
and am testing the fix now.
Thanks for fixinding this.
Tim
__
Camm,
What function in Axiom relies on this? I will fix it.
Tim
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
https://lists.nongnu.org/mailman/listinfo/axiom-developer
Greetings! I've resolved it now, but we should be aware of this going
forward.
axiom currently relies on a broken GCL implementation of functionp,
which incorrectly returns t for fboundp symbols. axiom uses this to
decide whether to funcall, as in (if (functionp x) (funcall x ...)).
With a corre
> Hi Tim! Working on 2.6.11, and did something to prevent the
> hashing/memoization from taking place in pascal.input, e.g. pn(50)
> hangs. How can I see what functions are being generated and trace the
> compiler? )lisp (trace compile) does not work.
The function you want is |genMapCode| in sr
Hi Tim! Working on 2.6.11, and did something to prevent the
hashing/memoization from taking place in pascal.input, e.g. pn(50)
hangs. How can I see what functions are being generated and trace the
compiler? )lisp (trace compile) does not work.
Take care,
--
Camm Maguire
