cc: [email protected]
Subject: Re: Re: [ast-developers] float i; (( i.MAX, i.MIN, i.EPSILON ))
constants?
--------
>
> Erm... doesn't this just require a small modification of the
> arithmetic engine (I don't know how to do the same for a plain
> ${i.MAX}), e.g. do a type-based (technically we "only" have six types
> - three integer and three float) lookup of the matching constant value
> if an integer name is followed by a '.' ?
>
>
First of all there are 9 types, 3 float, 3 integer, and 3 unsigned.
Secondly, it is much simpler of i.MAX only appears in arithmetic
expressions and cannot be used as ${i.MAX} because ${i.MAX} is
more complex because it needs to work with ${i.MAX op string}
and ${op i.MAX} as well.
I am not even sure how to implement ${!i.M*} given the current
architecture.
Maybe I should restrict b.true to arithmetic expressions only.
Programs that want ${i.MAX} can do $((i.MAX)).
Anyway, I have enough bug reports to keep me busy for now.
David Korn
[email protected]
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
