Near reference

From Erights

(Difference between revisions)
Jump to: navigation, search
(placeholder created. Q: should far and near references get their own pages?)
(merged near ref into this article)
 
Line 1: Line 1:
-
Place holder page for now see [http://www.erights.org/elib/concurrency/refmech.html Reference Mechanics]
+
'''Near''' is one of the three main [[reference state]]s, along with [[eventual reference|eventual]] and [[broken reference|broken]].
 +
 
 +
Near references designate objects in the same [[vat]], and so they can be the recipients of [[immediate call]]s. Near references cannot change [[reference state|state]] to [[broken reference|broken]].
 +
 
 +
Ordinary objects in the same vat (<code>[[LiteralExpr|"foo"]]</code>, <code>[[ObjectExpr|def foo {...}]]</code>, <code>[[ConstList|[1, 2, 3]]], etc.</code>) are near references.
 +
 
 +
see also [http://www.erights.org/elib/concurrency/refmech.html Reference Mechanics]
 +
 
 +
{{stub}}

Latest revision as of 01:10, 8 October 2008

Near is one of the three main reference states, along with eventual and broken.

Near references designate objects in the same vat, and so they can be the recipients of immediate calls. Near references cannot change state to broken.

Ordinary objects in the same vat ("foo", def foo {...}, [1, 2, 3], etc.) are near references.

see also Reference Mechanics

This page is a stub; it should be expanded with more information. If doing so, check the original E web site and the mailing list archives for content which could be moved into this page.
Personal tools
more tools