Now would be a good time to submit one ... :) http://wiki.axiom-developer.org/IssueTracker#addissue This might be due to a change in the underlying lisp semantics for PROBE-FILE and TRUENAME that wer
Since I modify spad code quite a lot, I know this message well. I didn't get round to write a bug report, though. It happens always when a compile succeeds and you want to compile a second time (sinc
Hello, I begin to test the manip.spad file (because I want to expand cos (2*x).) So I copy the manip.spad file in a local directory, add the silly lines in TRMANIP package ess : F -> F -- in the decl
Hi Bill: Thanks. I fixed the path and compiling problem by: (1) move the entire axiom directory to a different one j:\openaxiom\axiom from j:\Program Files\axiom (2) remove my old rm.exe from the h:\
William, Very Neat! Yes, this is a bug in the Windows version of Axiom caused by the fact that the Axiom code expects to be able to run unix system commands like `rm' (which means delete file). In th
In fact you just pointed a way to solve the problem! Notice that you are in effect constructing a domain! So first create this domain (call this anything else you like): --%PointedPrimeField )abbrev
Hi Camm. Ultimately, hopefully, and not this week. I suspect not as I had the same symptom 6 months ago with an earlier stable GCL (perhaps 2.6.2?). Perhaps some other bug since fixed which coinciden
Greetings! Mike, are the warnings not issues on Linux, or is the warning reporting code failing on Windows? If the latter, can we isolate to a lisp command? I think this is the pathname-name case iss
file's proposed directory did not exist. I solved this with "ENSURE-DIRECTORIES-EXIST" in the function "get-io-index-stream" in "src/interpreter/nlib.lisp.pamphlet" and when I left for work this mor