|
|
last edited 16 years ago by gdr |
1 2 3 4 5 6 7 | ||
Editor: gdr
Time: 2008/10/17 16:52:24 GMT-7 |
||
Note: Fixed in OpenAxiom |
added:
From gdr Fri Oct 17 16:52:24 -0700 2008
From: gdr
Date: Fri, 17 Oct 2008 16:52:24 -0700
Subject: Fixed in OpenAxiom
Message-ID: <20081017165224-0700@axiom-wiki.newsynthesis.org>
As I was looking for boolean simplification, I type )sh Expression Boolean. I get the list of the real expressions. So I type
sin (A::Expression Boolean) or true.
Line 1: sin (A::Expression Boolean) or true. ...................................A Error A: syntax error at top level Error A: Improper syntax. 2 error(s) parsing
Axiom disapproves
>> System error: Caught fatal error [memory may be damaged]?...
And the axiom process died the command-line after.
the axiom process died the command-line after.
This does not happen for me on at least the Windows version of Axiom.
But I do find it very odd that Axiom allows the construction of
the domain Expression Boolean
without complaint:
x:Expression Boolean:=true
(1) |
The scary sounding message: 'Caught fatal error [memory may be damaged]?' occurs for many operations applied to this object.
The definition of the constructor Expression R: OrderedSet
seems
wrong to me since there are may operations exported by Expression
that are not naturally interpreted over a domain that is just an
OrderedSet. For example Boolean
is considered ordered as follows:
Boolean has OrderedSet
(2) |
true > false
(3) |
although we might also question the wisdom of considering Boolean
ordered in this way.
The "memory may be damaged" message occurs quite often but I have yet to see any surface damage on the DIMM packages :-). I'm not sure why Bill thought this was a reasonable error message but it does not seem to be a problem. Only console interrupts have caused failure so far and those seem to be related to some race condition in garbage collection.
Tim
Status: open => fix proposed Status: fix proposed => fixed somewhereno patch available
http://fricas.svn.sourceforge.net/viewvc/fricas/trunk/src/interp/i-coerce.boot?r1=105&r2=189&view=patch