From: William Djaja Tjokroaminata <billtj@...>
Date: 2002-09-11T01:14:20+09:00
Subject: Re: Larry Wall's comments on Ruby

Oh yes, the consequence is there will more syntax in terms of
free-floating period (period with white space before and after), which
will be different from a period attached to its left operand, which still
can be used for method calls on strings.  I am not proposing this at
all; it just felt natural in Perl.

On the other hand, this additional syntax is not completely an exception
by itself.  There is already the "&" special syntax for Proc/block, which
is not strictly object-oriented.

Regards,

Bill
===========================================================================
dblack@candle.superlink.net wrote:
> Hi --

> On Wed, 11 Sep 2002, William Djaja Tjokroaminata wrote:

>> Agreed.  Until now, I still mistakenly use the "." operator from time to
>> time in Ruby, just because of the previous Perl experience, which was
>> very natural.

> But then what would Ruby use for method calls on strings?  Honestly, I
> don't think this can be cited as an example of an incorrect choice in
> Ruby.

> On the Perl topic: I knew I was definitely hooked on Ruby when I had
> occasion to write a Perl script and (a) left out semi-colons; (b)
> wrote calls to "puts"; (c) found myself writing things like:
> @array.map ... :-)