UninterpretedBytes.st
changeset 19101 8ccbefbc944d
parent 19047 035b338ef201
child 19104 e7c5169d9ab7
child 19196 1db38251aeb2
--- a/UninterpretedBytes.st	Mon Jan 25 19:51:21 2016 +0100
+++ b/UninterpretedBytes.st	Mon Jan 25 22:04:02 2016 +0100
@@ -81,28 +81,28 @@
 "
     UninterpretedBytes provides the common protocol for byte-storage
     containers; concrete subclasses are
-	ByteArray (which store the bytes within the Smalltalk object memory)
-	String    (knows that the bytes represent characters)
+        ByteArray (which store the bytes within the Smalltalk object memory)
+        String    (knows that the bytes represent characters)
     and
-	ExternalBytes (which store the bytes in the malloc-heap).
+        ExternalBytes (which store the bytes in the malloc-heap).
 
     UninterpretedBytes itself is abstract, so no instances of it can be created.
 
     [See also:]
-	ByteArray String ExternalBytes
+        ByteArray String ExternalBytes
 
     [author:]
-	Claus Gittinger
+        Claus Gittinger
 
     [Notice:]
-	Notice the confusion due to multiple methods with the same
-	functionality (i.e. 'xxxx:MSB:' vs. 'xxxx:bigEndian:').
-	The reason is that at the time this class was written,
-	ST80 sid not offer protocol to specify the byteOrder, and
-	ST/X provided methods ending in 'MSB:' for this.
-	In the meanwhile, VW added protocol ending in 'bigEndian:',
-	which has been added here for compatibility.
-	(certainly a point, where an ansi-standard will help)
+        Notice the confusion due to multiple methods with the same
+        functionality (i.e. 'xxxx:MSB:' vs. 'xxxx:bigEndian:').
+        The reason is that at the time this class was written,
+        ST80 did not offer protocol to specify the byteOrder, and
+        ST/X provided methods ending in 'MSB:' for this.
+        In the meanwhile, VW added protocol ending in 'bigEndian:',
+        which has been added here for compatibility.
+        (certainly a point, where an ansi-standard will help)
 "
 ! !