<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Aug 28, 2007, at 10:50 AM, Denis Kudriashov wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><BR><DIV><SPAN class="gmail_quote">2007/8/27, Alan Lovejoy <<A href="mailto:squeak-dev.sourcery@forum-mail.net">squeak-dev.sourcery@forum-mail.net</A>>:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Denis Kudriashov wrote:<BR>> Smalltalk is wonderfull language. We can implement any ideas without<BR>> making changes in language (as Java or C# live).<BR>> I think pipes is very usefull in DSL implementation and usage, simpler <BR>> and fast object inspecting. But long message chaines in domain code<BR>> are bad smell<BR><BR>There haven't been all that many syntax changes to Smalltalk since its<BR>public release as ST80. Off the top of my head, I can list the following: <BR><BR></BLOCKQUOTE></DIV><BR><BR>These changes does not have an influence on language core, language semantics. Its just was some convenient constructions for building special objects. But when we put in Smalltalk new operator we change it semantics. Why we must do it? <SPAN class="gmail_quote"><BR>Bert implemented it in clean Smalltalk without any language changes. Why it is not </SPAN><SPAN style="color: rgb(128, 128, 128);">enough?</SPAN><BR><SPAN class="gmail_quote"><BR></SPAN>Best regards, <BR>Denis<BR><BR><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> </BLOCKQUOTE></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Well said.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>My view is that adding the pipe you asserting that chained functional applications are good and should be used more. Is this what you want ?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The good tricks we have seen are not enough for me because I don't like the cascade to change it's meaning while reading.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>on the pipe (which I look at as beautiful hack)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I't like making the question mark become an exclamation mark because there was a special keyword (asPipe). </DIV><DIV>"!" and "?" are both terminators and I don't like their meaning to be switched while reading.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Then I think that chained applications of functions is good way to reuse methods. </DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Fabio Filasieno</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN> </DIV><BR></BODY></HTML>