#262 timeMachine can't be persisted

closed-fixed
9
2005-07-24
2005-07-18
Steve Jenson
No

FIXED
get "can't uneval timeMachine" when you try to use a
timeMachine in an optUncall. In 0.8.30d

Followups

Comment Date By
Fixed as of 0.8.31b

The problem occurs when adding an unsettled reference
as a key to a CycleBreaker. addExit has now been
overloaded to facilitate catching this case. The case
occurred because we were building the exits table for
the timeMachine before creating the timeMachine, so at
that moment we had a promise for the timeMachine, which
doesn't match a resolved timeMachine.

We should probably make the non-upwards compatible
change to have addExit default to the safe way rather
than the permissive way. 2004-Sep-15 10:07 markm

Discussion

  • Steve Jenson
    Steve Jenson
    2005-07-18

    • status: open --> open-fixed
     
  • Steve Jenson
    Steve Jenson
    2005-07-18

    • status: open-fixed --> closed-fixed
     
    • assigned_to: nobody --> caplet