<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 12:30 AM, Bert Freudenberg wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">With the generic pipe object from my change-set in the original thread this gets you both - no need to define new methods:</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>highestNumberedChangeSet</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>"ChangeSorter highestNumberedChangeSet"</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>^self allChangeSetNames asPipe</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>select:[:aString | aString startsWithDigit];</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>collect:[:aString | aString initialIntegerOrNil];</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>ifNotEmpty:[:list | list max]</FONT></P> </BLOCKQUOTE></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><BR class="khtml-block-placeholder"></DIV><DIV>I have to admit that the asPipe idea is really cool and it might do the trick.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>A minor minor thing: you still need to explain it, and it's better to have 1 syntax token attached to 1 meaning.</DIV><DIV>Is a bit ugly that cascade changes it's meaning: sometimes does X, some times does Y.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Still the asPipe is a very very nice hack.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think the question is different from adding or not syntax to do a trick.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Do Small-talkers want to assert:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>"Use functional programming when possible"</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>or not ?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><DIV>This is question. And I can't answer that.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>It's not :</DIV><DIV>"Shall we add a new syntax token to do the trick ?"</DIV></DIV></SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV>Fabio FIlasieno<BR><DIV><BR class="khtml-block-placeholder"></DIV><DIV>PS. Note that I associate functional programming with a chained application of functions (better if pure)</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>