|
|
|
last edited 10 years ago by test1 |
Edit detail for #208 interpret(x::InputFor)=x is broken for functions and types revision 4 of 4
| 1 2 3 4 | ||
|
Editor: test1
Time: 2014/04/23 19:08:01 GMT+0 |
||
| Note: | ||
added:
From test1 Wed Apr 23 19:08:01 +0000 2014
From: test1
Date: Wed, 23 Apr 2014 19:08:01 +0000
Subject:
Message-ID: <20140423190801+0000@axiom-wiki.newsynthesis.org>
Severity: normal => minor
The coersion to InputForm produces a lispy representation for most types. E.g.
axiom
)set output tex off
axiom
)set output algebra on
axiom
p:POLY INT:=x^2+1
2 (1) x + 1
Type: Polynomial(Integer)
axiom
pSex:=p::InputForm
(2) (+ (^ x 2) 1)
Type: InputForm
axiom
p1:=interpret(pSex)
2 (3) x + 1
Type: Polynomial(Integer)
But this fails for functions
axiom
f:INT->INT
Type: Void
axiom
f(x) == x^2+1
Type: Void
axiom
-- force compile f(2)
axiom
Compiling function f with type Integer -> Integer
(6) 5
Type: PositiveInteger
axiom
fSex:=f::InputForm
(7) (coerceOrCroak (CONS '(Mapping (Integer) (Integer)) (wrap (MAP (#1 + (^ #1 2) 1)))) '(InputForm) 'noMapName)
Type: InputForm
So far so good, but
axiom
f1:=interpret(fSex)
Cannot convert from type (Integer -> Integer) to InputForm for value theMap(MAP)
... --kratt6, Fri, 28 Dec 2007 15:10:20 -0800 reply
Category: Aldor Library Compiler => Axiom Library
This is a problem with AXIOMs? not making their minds about whether
a map should be treated as a value in its own, or whether it is an expression
that needs further evaluation to yield a value.
The proper fix is to have all user defined maps treated as
values in their owns -- e.g. their representation in the
interpreter environment should be wrapped. However, that requires a
more extensive patch to implement. But, that is the right thing to do.
Severity: normal => minor