Axiom Computer Algebra System - Bugs: bug #6903, Category compiles with the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #6903: Category compiles with the compiler but not within the interpreter
Submitter: | David Mentré <dmentre> | ||
Submitted: | Mon 01 Dec 2003 09:38:44 PM UTC | ||
Category: | interpreter | Severity: | 2 - Minor |
Item Group: | code bug | Status: | Wont Fix |
Privacy: | Public | Assigned to: | None |
Originator Name: | Stefan Dirnstorfer | Open/Closed: | Closed |
Release: | October 31st binary release | Reproducibility: | None |
Fixed Release: | |||
Error message: | Internal Error
|
||
Example of code trigerring the bug: | )abbrev category MYCAT MyCat
|
||
Internal cause: |
|
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2008-11-25 | axiom | Status | None | Wont Fix | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
You can correctly compile this code by making a file (say, f.spad) thus:
)abbrev category MYCAT MyCat
MyCat:Category == with { new: ()->% }
The system needs the ")abbrev" line.
Then do:
)co f.spad
The code compiles within a file (with above procedure), but not under the interpreter.
Additionnal explanation from Tim:
Yes, the code can compile from a file.
No, the code cannot be compiled from the interpreter.
Is this a bug?
ummm, yes, no, maybe? Yes, in theory the interpreter should accept
the function and compile it. No, the interpreter won't accept the
function and compile it. Maybe that's a bug or it's a design flaw.
The problem is that the compiler and the interpreter have different
parsers. Since they have different goals they have different constraints.
So unifying the two parsers is not a simple problem. I'll look at the
specific error but I'm not certain what the fix will be.