Re: Newbie questions about persistence

On Thu, Sep 17, 2009 at 3:06 PM, Kevin Reid <[email protected]> wrote:
> On Sep 17, 2009, at 8:23, Thomas Leonard wrote:
>> On Thu, 2009-09-17 at 10:21 +0100, Thomas Leonard wrote:
>>> On Mon, 2009-09-14 at 15:43 -0400, Kevin Reid wrote:
>> [...]
>>>> exposing its existence to the user. (One way to do it would be to
>>>> have
>>>> your oneShot serialize, not as its current state, but rather the
>>>> slot
>>>> of the used flag: def uncall := [makeOneShot, "withFlagSlot",
>>>> [&used]]. Then the 'used' slot object serves as the un-duplicatable
>>>> object.
>>>
>>> That's clever - thanks!
>>
>> Oops. I spoke too soon. Looks like only final slots can be persisted:
>>
>> #   . <makeRef>.fulfillment(<ref broken by problem: Can't uneval
>> <var false>>)
>
> Gah. Sometimes I forget what's my own invention.
>
> MarkM, is there any reason not to add __optUncall to (unguarded) var
> slots?

I don't believe so. This seems like a good idea to me.


-- 
Text by me above is hereby placed in the public domain

    Cheers,
    --MarkM