From c66c3c82fda2f68e5aac62d16657d8a77e6d91ee Mon Sep 17 00:00:00 2001 From: Marcos Magueta Date: Sun, 11 Oct 2026 01:30:27 -0300 Subject: update docs --- docs/object-system.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/object-system.org') diff --git a/docs/object-system.org b/docs/object-system.org index a2f7929..facdda0 100644 --- a/docs/object-system.org +++ b/docs/object-system.org @@ -134,7 +134,7 @@ RNT exposes its resources as a hierarchy of objects. The root of this tree is an #+end_src =register= and =unregister=, as implemented by the root of the hierarchy, allows components to register resources that can be retrieved by users of the system through the corresponding =Directory= interface. The handle passed as an argument to =register= must support being "copy"ed. -As a convenience, a =path= represents a pattern of traversal the object tree. The path ="branch" @/ "master" @/ "multigroup" @/ "universe" @/ this= represents the object that can be retrieved by, from a given reference point, "open"ing the child denoted by ="branch"= on the given reference point, then "open"ing the child denoted ="master"= on the retrieved object, and so on. Every traversal assumes that the object in question has a =Directory= protocol. The ability to construct and manipulate paths is implemented by the =Path= module: +As a convenience, a =path= represents a pattern of traversal the object tree. The path ="system" @/ "branch" @/ "master" @/ "multigroup" @/ "universe" @/ this= represents the object that can be retrieved by, from a given reference point, "open"ing the child denoted by ="system"= on the given reference point, then "open"ing the child denoted ="branch"= on the retrieved object, and so on. Every traversal assumes that the object in question has a =Directory= protocol. The ability to construct and manipulate paths is implemented by the =Path= module: #+begin_src ocaml module Path : sig type path -- cgit v1.2.3