--- a/MessageSend.st Mon Oct 10 01:29:28 1994 +0100
+++ b/MessageSend.st Mon Oct 10 01:53:52 1994 +0100
@@ -21,7 +21,7 @@
COPYRIGHT (c) 1994 by Claus Gittinger
All Rights Reserved
-$Header: /cvs/stx/stx/libbasic/MessageSend.st,v 1.1 1994-08-05 01:06:59 claus Exp $
+$Header: /cvs/stx/stx/libbasic/MessageSend.st,v 1.2 1994-10-10 00:53:52 claus Exp $
'!
!MessageSend class methodsFor:'documentation'!
@@ -42,7 +42,7 @@
version
"
-$Header: /cvs/stx/stx/libbasic/MessageSend.st,v 1.1 1994-08-05 01:06:59 claus Exp $
+$Header: /cvs/stx/stx/libbasic/MessageSend.st,v 1.2 1994-10-10 00:53:52 claus Exp $
"
!
@@ -58,6 +58,7 @@
However, the send-operation itself is faster in a block, since it
will use a better caching scheme (inline-cache) for its send, while
sending here is done with a #perform:, which is not inline-cached.
+ Thus it is not sure, which one is faster in the end ...
Example:
@@ -85,7 +86,7 @@
receiver:r selector:sel arguments:argArray
|newMessage|
- newMessage := super selector:sel arguments:argArray.
+ newMessage := super setSelector:sel arguments:argArray.
newMessage receiver:r.
^ newMessage
! !
@@ -93,7 +94,7 @@
!MessageSend methodsFor:'evaluation'!
value
- "evaluate the messagesend"
+ "evaluate the messagesend with the original arguments"
^ receiver perform:selector withArguments:args
!
@@ -105,13 +106,15 @@
!
value:arg1 value:arg2
- "evaluate the messagesend, with arg1 and arg2 instead of the original"
+ "evaluate the messagesend, with arg1 and arg2 instead of the original
+ arguments"
^ receiver perform:selector with:arg1 with:arg2
!
value:arg1 value:arg2 value:arg3
- "evaluate the messagesend, with arg1, arg2 and arg3 instead of the original"
+ "evaluate the messagesend, with arg1, arg2 and arg3 instead of the original
+ arguments"
^ receiver perform:selector with:arg1 with:arg2 with:arg3
! !
@@ -145,4 +148,3 @@
aStream nextPutAll:'>>'.
selector printOn:aStream
! !
-