MathAction #208 interpret(x::InputFor)=x is broken for functions and types

Topics

FrontPage
- IssueTracker
  - #208 interpret(x::InputFor)=x is broken for functions and types <-- You are here.

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

... --gdr, Mon, 19 May 2008 20:16:44 -0700 reply

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.

... --test1, Wed, 23 Apr 2014 19:08:01 +0000 reply

Severity: normal => minor

Subject: Be Bold !!

	( 14 subscribers )