Remove potentially confusing sentence in __mangling description.

This commit is contained in:
Georg Brandl 2009-08-13 12:57:25 +00:00
parent fb69631af7
commit aa66a968d4
1 changed files with 2 additions and 5 deletions

View File

@ -549,11 +549,8 @@ such a mechanism, called :dfn:`name mangling`. Any identifier of the form
``__spam`` (at least two leading underscores, at most one trailing underscore) ``__spam`` (at least two leading underscores, at most one trailing underscore)
is textually replaced with ``_classname__spam``, where ``classname`` is the is textually replaced with ``_classname__spam``, where ``classname`` is the
current class name with leading underscore(s) stripped. This mangling is done current class name with leading underscore(s) stripped. This mangling is done
without regard to the syntactic position of the identifier, so it can be used to without regard to the syntactic position of the identifier, as long as it
define class-private instance and class variables, methods, variables stored in occurs within the definition of a class.
globals, and even variables stored in instances. Truncation may occur when the
mangled name would be longer than 255 characters. Outside classes, or when the
class name consists of only underscores, no mangling occurs.
Note that the mangling rules are designed mostly to avoid accidents; it still is Note that the mangling rules are designed mostly to avoid accidents; it still is
possible to access or modify a variable that is considered private. This can possible to access or modify a variable that is considered private. This can