Compatibility: use `#instVarNames` instead of `#instanceVariableNames`
authorJan Vrany <jan.vrany@labware.com>
Thu, 13 Jul 2023 16:00:06 +0100
changeset 283 a4b362ab3a2a
parent 282 b3bec4a241ef
child 284 2ce4c992fcc8
Compatibility: use `#instVarNames` instead of `#instanceVariableNames` ...as the latter does not exists in (at least) Pharo.
GDBCommandResult.st
--- a/GDBCommandResult.st	Thu Jul 13 15:45:49 2023 +0100
+++ b/GDBCommandResult.st	Thu Jul 13 16:00:06 2023 +0100
@@ -99,7 +99,7 @@
 
     "/ We shoud ignore `status` or `command` instvars 
     "/ these are used for other purposes here.
-    (name ~= #value and:[self class instanceVariableNames includes: name]) ifTrue:[ 
+    (name ~= #value and:[self class instVarNames includes: name]) ifTrue:[ 
         properties isNil ifTrue:[ ^ nil ].
         ^ properties at: name ifAbsent: [ nil ].
     ]. 
@@ -114,7 +114,7 @@
     "/ We shoud not set `status` or `command` instvars even if
     "/ command response contains 'property' with that names -
     "/ these are used for other purposes here.
-    (name ~= #value and:[self class instanceVariableNames includes: name]) ifTrue:[ 
+    (name ~= #value and:[self class instVarNames includes: name]) ifTrue:[ 
         properties isNil ifTrue:[ 
             properties := Dictionary new.
             properties at: name put: val.