<br><br><div><span class="gmail_quote">2007/8/27, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just for fun - the tiny attached change-set allows #asPipe to get<br>piping behavior for cascades:<br><br>Squeak asPipe<br> ps: 'aux';<br> grep: 'fabio';<br> sort<br><br>It makes these two expressions equivalent
<br><br> ((((4 + 2) * 3) + 3) * 2)<br><br> 4 asPipe + 2; * 3; + 3; * 2<br><br>Now I wouldn't use this in production but for interactive exploration<br>it might actually be useful. Similar to implementing Symbol>>#value:
<br>to allow "(1 to: 10) collect: #squared".<br><br>Btw, did you know each class can declare its own parser and compiler<br>class? Experimenting with the syntax does not necessarily have to<br>break other's stuff.
<br><br>- Bert -<br><br><br></blockquote></div>It's very cool. <br>Smalltalk is wonderfull language. We can implement any ideas without making changes in language (as Java or C# live).<br>I think pipes is very usefull in DSL implementation and usage, simpler and fast object inspecting. But long message chaines in domain code are bad smell
<br><br>