--- a/String.st Sat Jul 27 15:45:37 2019 +0200
+++ b/String.st Sat Jul 27 16:30:06 2019 +0200
@@ -139,16 +139,16 @@
Strings are kind of kludgy: to allow for easy handling by C functions,
there is always one 0-byte added at the end, which is not counted
- in the strings size, and is not accessible from the smalltalk level.
- This guarantees, that a smalltalk string can always be passed to a
- C- or a system api function without danger (of course, this does not
- prevent a nonsense contents ...)
+ in the string's size, and is not accessible from the Smalltalk level.
+ This guarantees, that a Smalltalk string can always be passed to a
+ C- or a system api function without danger
+ (of course, this does not prevent a nonsense contents...)
You cannot add any instvars to String, since the run time system & compiler
creates literal strings and knows that strings have no named instvars.
If you really need strings with instVars, you have to create a subclass
of String (the access functions defined here can handle this).
- A little warning though: not all smalltalk systems allow subclassing String,
+ A little warning though: not all Smalltalk systems allow subclassing String,
so your program may become unportable if you do so.
Strings have an implicit (assumed) encoding of ISO-8859-1.
@@ -161,11 +161,11 @@
processing a String containing the 0-byte.
[author:]
- Claus Gittinger
+ Claus Gittinger
[see also:]
- Text StringCollection TwoByteString JISEncodedString
- Symbol
+ Text StringCollection TwoByteString JISEncodedString
+ Symbol
"
! !
@@ -526,6 +526,8 @@
! !
+
+
!String class methodsFor:'queries'!
defaultPlatformClass
@@ -546,6 +548,10 @@
! !
+
+
+
+
!String methodsFor:'accessing'!
at:index
@@ -5103,6 +5109,7 @@
"Modified (comment): / 01-05-2017 / 14:05:41 / cg"
! !
+
!String methodsFor:'substring searching'!
caseInsensitiveIndexOfSubCollection:aSubString startingAt:startIndex ifAbsent:exceptionValue
@@ -5408,6 +5415,7 @@
! !
+
!String class methodsFor:'documentation'!
version