AtomicContext

This function is used when implementing a naming system that supports junctions. For example, when the a_list_nns(newobj) method is invoked, that means the caller is attempting to list the the nns context of of this context. For a context that supports junctions, it by default does not have any nns. Consequently, a NameNotFoundException is thrown.

This function is used when implementing a naming system that supports junctions. For example, when the a_bind_nns(name, newobj) method is invoked, that means the caller is attempting to bind the object 'newobj' to the nns of 'name'. For context that supports junctions, 'name' names a junction and is pointing to the root of another naming system, which in turn might have an nns. This means that a_bind_nns() should first resolve 'name' and attempt to continue the operation in the context named by 'name'. (i.e. bind to the nns of the context named by 'name'). If name is already empty, then throw NameNotFoundException because this context by default does not have any nns.

Resolves the nns for 'name' when the named context is acting as an intermediate context. For a system that supports junctions, this would be equilvalent to a_lookup(name, cont); because for junctions, an intermediate slash simply signifies a syntactic separator. For a system that supports implicit nns, this would be equivalent to a_lookup_nns(name, cont); because for implicit nns, a slash always signifies the implicit nns, regardless of whether it is intermediate or trailing. By default this method supports junctions, and also allows for an implicit nns to be dynamically determined through the use of the "nns" reference (see a_processJunction_nns()). Contexts that implement implicit nns directly should provide an appropriate override.

Parse 'inputName' into two parts: head: the first component in this name tail: the rest of the unused name. Subclasses should provide an implementation for this method which parses inputName using its own name syntax.

Resolves the nns for 'name' when the named context is acting as an intermediate context. For a system that supports only junctions, this would be equilvalent to c_lookup(name, cont); because for junctions, an intermediate slash simply signifies a syntactic separator. For a system that supports only implicit nns, this would be equivalent to c_lookup_nns(name, cont); because for implicit nns, a slash always signifies the implicit nns, regardless of whether it is intermediate or trailing. By default this method supports junctions, and also allows for an implicit nns to be dynamically determined through the use of the "nns" reference (see c_processJunction_nns()). Contexts that implement implicit nns directly should provide an appropriate override. A junction, by definition, is a binding of a name in one namespace to an object in another. The default implementation of this method detects the crossover into another namespace using the following heuristic: there is a junction when "name" resolves to a context that is not an instance of this.getClass(). Contexts supporting junctions for which this heuristic is inappropriate should override this method.

Resolve to context named by 'name'. Returns true if at named context (i.e. 'name' is empty name). Returns false otherwise, and sets Continuation on parts of 'name' not yet resolved.

Resolves to nns associated with 'name' and set Continuation to the result.

Resolves to penultimate context named by 'name'. Returns true if penultimate context has been reached (i.e. name only has one atomic component left). Returns false otherwise, and sets Continuation to parts of name not yet resolved.

This function is similar to resolve_to_penultimate_context() except it should only be called by the nns() functions. This function fixes any exception or continuations so that it will have the proper nns name.