Re: Tetrits and "stickiness"

["Nate Hayes" <nh@xxxxxxxxxxxxxxxxx>]

Michel Hack wrote:
> Nate Hayes wrote:
> > Michel Hack wrote:
> > > In fact, programs DO care about both, at SEPARATE times.  A common
> > > situation is a fast path that expects no exceptional cases, but
> > > checks this assumption with a sticky check at the end so as to
> > > repeat the routine using a slow but thoroughly-checked sequence.
> >
> > > Are you (and Ian) talking strictly about decorations,
> > > or of bare intervals, as well?
>
> This is strictly about decorations with "tetrits" or even "octits",
> which are capable of capturing both last-operation details and sticky
> information about various attributes.  This goes beyond the "trits"
> of Motion 8.

Ok.

In that case, when the routine is repeated, can't the debugger just manually 
reset the decoration of each input interval during the slow but 
thoroughly-checked sequence? For example:

   -- make a local copy of the decoration representing the most recent 
operation
   -- reset the input decoration of each operand
   -- perform the operation
   -- check the result of the operation
   -- lather, rinse, repeat...

Nate