On Thu, Feb 12, 2015 at 1:22 AM, Matt Oliveri <[email protected]> wrote: > On Thu, Feb 12, 2015 at 3:10 AM, Matt Rice <[email protected]> wrote: >> it may be interesting to note Marc Stiegler's implementation of >> sealer/unsealer pairs using currying and side effects, as discussed by >> Norm here: >> http://cap-lore.com/Languages/Synergy/OCaml.html > > I can't figure out why the unsealer sets content to nullObj again > after it reads it. Does anyone know?
in the unseal function the first content := nullObj; call seems to be there to protect a previously unsealed value by let bar () = ();; unseal(bar);; (calling the unsealer with a box that doesn't produce the effect) and I believe the 2nd call is there so that if you can cause someone else to cause the effect, you cannot invoke their function that causes the effect from within the filledbox () call and take their sealed value that you do not have _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
