> Might the default rate be better selected by using the rate of the LHS of the
> expression? At least a situation like mine would be covered. Is there some
> reasoning behind this default?
Just a guess, but I'm assuming this idea in its more general form
(i.e. as a last resort, a polymorphic opcode takes on the rate of
the statement that its in) has the problem that for some statements,
the rate of the statement is tied to the rate of the expression in
it. So, you could get an undecidable case, where the statement rate
depends on the expression rate, but the expression rate depends on
the statement rate. The "null assignment" statement is an obvious
example, a few other statements may have this problem too.
But its true that for the specific case of an assignment statement,
there are no (immediately obvious, rate semantics is too tricky to
say "none" without a day's thought :-) problems with this approach.
> Might there be a need for a "time-cast" operation? This might be done as
> follows:
I like the general "rate-cast" idea (it's bounced around in the past on
saol-devs), I should go prototype it to see how it works in practice ...
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 12:11:07 EST