Double semicolon also was my original choice for the change set I sent
yesterday, as the comment in Parser>>pipe attests. The concern that
made me change it to :> was the similarity of ; and ;;. It may sound
good from the logical point of view, in practice I'm afraid it can be
a source of bugs. Anyway, here is the full set that does ;; as well as
:>.

--Vassili

On 8/27/07, Ron Teitelbaum <Ron at usmedrec.com> wrote:
> +1
>
> ; returns self
> ;; returns result is very clean, easy to remember and teach.
>
> Ron
>
> > -----Original Message-----
> > From: Bert Freudenberg
> >
> > On Aug 26, 2007, at 19:10 , David Mitchell wrote:
> >
> > > I like the :> and the double semi (and I also like Bert's asPipe).
> >
> > Hehe. Thanks. For those who did not look at my change-set: It did not
> > touch the Compiler at all or modify the syntax. It was strictly
> > Smalltalk (with #asPipe returning a proxy object).
> >
> > Personally I find ";;" quite fitting.  To me, ":>" looks still
> > selector-like.
> >
> > I'd rather not use "_" as it would make a useful character to allow
> > for in selectors later (for simpler interaction with other languages).
> >
> > - Bert -
> >
> >
>
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PipeWithDoubleSemi.1.cs
Type: application/octet-stream
Size: 2779 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20070827/eb2bbd2d/PipeWithDoubleSemi.1.obj