Author: lwall
Date: 2010-04-05 19:16:34 +0200 (Mon, 05 Apr 2010)
New Revision: 30317

Modified:
   docs/Perl6/Spec/S02-bits.pod
Log:
[S02] rename ObjID to ObjAt to reduce possibility of collision with user types


Modified: docs/Perl6/Spec/S02-bits.pod
===================================================================
--- docs/Perl6/Spec/S02-bits.pod        2010-04-05 17:07:39 UTC (rev 30316)
+++ docs/Perl6/Spec/S02-bits.pod        2010-04-05 17:16:34 UTC (rev 30317)
@@ -590,7 +590,7 @@
 or any other mundane value type).  Nor should we be encouraging people
 to think of object locations that way in any case.  So C<WHICH> still
 returns a value rather than another object, but that value must be of
-a special C<ObjID> type that prevents accidental confusion with normal
+a special C<ObjAt> type that prevents accidental confusion with normal
 value types, and at least discourages trivial pointer arithmetic.
 
 Certainly, it is difficult to give a unique name to every possible
@@ -598,7 +598,7 @@
 a space.  In the absence of a universal naming scheme, it can only
 be made improbable that two addresses from two different spaces will
 collide.  A sufficently large random number may represent the current
-address space on output of an C<ObjID> to a different address space,
+address space on output of an C<ObjAt> to a different address space,
 or if serialized to YAML or XML.  (This extra identity component
 need not be output for debugging messages that assume the current
 address space, since it will be the same big number consistently,

Reply via email to