Comments on: Selectors as Blocks http://blog.3plus4.org/2007/03/27/selectors-as-blocks/ The neighbourhood of 7 Fri, 03 Sep 2010 02:00:37 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: For.example » Blog Archive » Cyclomatic Complexity in Languages with Closures http://blog.3plus4.org/2007/03/27/selectors-as-blocks/comment-page-1/#comment-1736 For.example » Blog Archive » Cyclomatic Complexity in Languages with Closures Wed, 11 Nov 2009 12:08:53 +0000 http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-1736 [...] if you are using selectors as blocks you might even get multiple path without a block, as for [...] [...] if you are using selectors as blocks you might even get multiple path without a block, as for [...]

]]> By: Adrian http://blog.3plus4.org/2007/03/27/selectors-as-blocks/comment-page-1/#comment-1735 Adrian Wed, 11 Nov 2009 09:38:58 +0000 http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-1735 Cool stuff Vassili. You might even use the compiler to get rid of the manual #perform: in the blocks and thus speed up loops. Also nice is to use the same for sort blocks, Symbol >> asSortBlock "Answer a sort block, which evaluates this symbol for both arguments and compares the resulting values" | stream | stream := (String new: self size * 2 + 14) writeStream. stream nextPutAll: '[:a :b|a '; nextPutAll: self; nextPutAll: '<=b '; nextPutAll: self; nextPut: $]. ^Compiler evaluate: stream contents Cool stuff Vassili. You might even use the compiler to get rid of the manual #perform: in the blocks and thus speed up loops. Also nice is to use the same for sort blocks,

Symbol >> asSortBlock
“Answer a sort block, which evaluates this symbol for both arguments
and compares the resulting values”
| stream |
stream := (String new: self size * 2 + 14) writeStream.
stream
nextPutAll: ‘[:a :b|a ';
nextPutAll: self;
nextPutAll: '<=b ';
nextPutAll: self;
nextPut: $].
^Compiler evaluate: stream contents

]]> By: Travis Griggs http://blog.3plus4.org/2007/03/27/selectors-as-blocks/comment-page-1/#comment-16 Travis Griggs Wed, 28 Mar 2007 17:57:35 +0000 http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-16 That's cool Vassili. I still like the simplicity of Symbol>>value of course. But I like the asBlock pattern for the bigger items. Thogh I use them less. You rightly point out that it gets us around the code that "checks" for numArgs. To me, this is where the real fault lies at though. The numArgs API is ambiguous based on the intended use as an either a selector or an evaluator. That’s cool Vassili. I still like the simplicity of Symbol>>value of course. But I like the asBlock pattern for the bigger items. Thogh I use them less.

You rightly point out that it gets us around the code that “checks” for numArgs. To me, this is where the real fault lies at though. The numArgs API is ambiguous based on the intended use as an either a selector or an evaluator.

]]> By: Vassili Bykov http://blog.3plus4.org/2007/03/27/selectors-as-blocks/comment-page-1/#comment-15 Vassili Bykov Wed, 28 Mar 2007 16:52:51 +0000 http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-15 Sure, but that doesn't solve the problem of numArgs breaking the illusion. Sure, but that doesn’t solve the problem of numArgs breaking the illusion.

]]> By: Alan Knight http://blog.3plus4.org/2007/03/27/selectors-as-blocks/comment-page-1/#comment-14 Alan Knight Wed, 28 Mar 2007 16:20:32 +0000 http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-14 I don't understand why this is better than Symbol>>value: for multiple-argument selectors. It seems to me that you can do exactly the same thing by implementing Symbol>>value:value: I don’t understand why this is better than Symbol>>value: for multiple-argument selectors. It seems to me that you can do exactly the same thing by implementing Symbol>>value:value:

]]>