aboutsummaryrefslogtreecommitdiffstats
path: root/docs/object-system.org
diff options
context:
space:
mode:
authorMarcos Magueta <maguetamarcos@gmail.com>2026-10-11 01:30:27 -0300
committerMarcos Magueta <maguetamarcos@gmail.com>2026-10-11 01:30:27 -0300
commitc66c3c82fda2f68e5aac62d16657d8a77e6d91ee (patch)
treeb2351bcb319f6885a8d93930af6d72cf603250fa /docs/object-system.org
parentcc0b15c84de8b866cccd8b660b0ce0afcfba3d98 (diff)
downloadRNT-c66c3c82fda2f68e5aac62d16657d8a77e6d91ee.tar.gz
RNT-c66c3c82fda2f68e5aac62d16657d8a77e6d91ee.zip
update docs
Diffstat (limited to '')
-rw-r--r--docs/object-system.org2
1 files changed, 1 insertions, 1 deletions
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