summaryrefslogtreecommitdiff
path: root/naming_context.mdwn
blob: be04121134791fa6b499d4f86716eedbefaafa79 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
[[license text="""
Copyright © 2007 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the
terms of the GNU Free Documentation License, Version 1.2 or any later version
published by the Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and no Back-Cover Texts.  A copy of the license is included
in the section entitled [[GNU_Free_Documentation_License|/fdl.txt]].

By contributing to this page, you agree to assign copyright for your
contribution to the Free Software Foundation.  The Free Software Foundation
promises to always use either a verbatim copying license or a free
documentation license when publishing your contribution.  We grant you back all
your rights under copyright, including the rights to copy, modify, and
redistribute your contributions.
"""]]

Names are bindings to objects, however, to find an object
given a name, the relation must be looked up in a
naming context.  A problem with using string as names is
that it is very easy to lose track of the correct naming
context.  This is one of the problem with [[PassiveTranslators]]:
a passive translator is a string.  When the node is accessed
on which the passive translator is set and there is no active
translator, then an active translator is started using the
passive translator setting.  The active translator is started
by the file system, not the program instance that set the
passive translator.  The passive translator settings are
therefore resolved in the file system's naming context, which
may be different from that of the program instance that set the
passive translator setting.