On Sun, Dec 05, 2004 at 10:02:16AM -0600, Rod Adams wrote:
> Although I by no means dispute that longest token rule is a long term
> standard in language design, I will claim that many programmers,
> including myself before this, are unaware of it.
Programmers tend to follow the rule even when t
Larry Wall wrote:
<>On Sat, Dec 04, 2004 at 08:55:00PM -0600, Rod Adams wrote:
: $x ==<$foo>; # $x == <$foo>; $x = =<$foo>;
: @x <==<$foo>; # @x <= =<$foo>; @x <== <$foo>;
: $x//=<$foo>; # $x // =<$foo>; $x //= <$foo>;
: [EMAIL PROTECTED]; # $x ** [EMAIL PROTECTED]; $x **= @y;
In each of those c
On Sat, Dec 04, 2004 at 08:55:00PM -0600, Rod Adams wrote:
: Larry Wall wrote:
:
: >On Sat, Dec 04, 2004 at 08:14:17PM -0600, Rod Adams wrote:
: >: In fact, unary = imposes whitespace requirements on all ops that end in
: >=.
: >
: >Not true.
: >
: I guess not all cases. But several do in certai
Larry Wall wrote:
On Sat, Dec 04, 2004 at 08:14:17PM -0600, Rod Adams wrote:
: In fact, unary = imposes whitespace requirements on all ops that end in =.
Not true.
I guess not all cases. But several do in certain situations.
$x ==<$foo>; # $x == <$foo>; $x = =<$foo>;
@x <==<$foo>; # @x <= =<$
On Sat, Dec 04, 2004 at 08:14:17PM -0600, Rod Adams wrote:
: In fact, unary = imposes whitespace requirements on all ops that end in =.
Not true.
Larry
Alexey Trofimenko wrote:
On Sat, 04 Dec 2004 11:03:03 -0600, Rod Adams <[EMAIL PROTECTED]> wrote:
Okay, this rant is more about the \s<\s than \s=\s. To me, it is
easier to understand the grouping of line 1 than line 2 below:
if( $a<$b && $c<$d ) {...}
if( $a < $b && $c < $d ) {...}
In line2, my
