Of course I can :)

In perl6 the opening paren (() of a function cannot be separated from the function by whitespace:

Legal in perl5:

 my $foo = foo( 1 );          # A
 my $foo = foo(1);            # B
 my $foo = foo (1);           # C
 my $foo = foo      (    1    # D
           );
[download]

For reasons I explain in my style guide MY preference is C. Perl6 only supports A and B.

This is only an example. The syntax rules go deeper than that, causing the dot (.) to be special too, so that

my $foo = $object->method (1)
                 ->method (2)
                 ->method (3);
[download]

chaining as allowed in perl5 (break to a newline wherever you like), would NOT translate to

my $foo = $object.method(1)
                 .method(2)
                 .method(3);
[download]

This is bad (IMHO), see:

$ cat t.pl
use v6;

class C {
   has Int $.x is rw = 0;

   method foo (Int $i) { $!x += $i; return self; }
   method bar (Int $i) { $!x -= $i; return self; }
   }

C.new().foo(1).bar(2).say;
$ perl6 t.pl
C.new(x => -1)
$ cat t.pluse v6;

class C {
   has Int $.x is rw = 0;

   method foo (Int $i) { $!x += $i; return self; }
   method bar (Int $i) { $!x -= $i; return self; }
   }

C.new()
 .foo(1)
 .bar(2)
 .say;
$ perl6 t.pl
===SORRY!=== Error while compiling t.pl
Two terms in a row
at t.pl:11
------>  ⏏.foo(1)
    expecting any of:
        infix stopper
        infix or meta-infix
        statement end
        statement modifier
        statement modifier loop
[download]

This is because a leading dot (after whitespace) will see the next word as method on the current topic ($_) instead of as a method on the previvious "thing". As the previous line has no trailing semi-colon, I would prefer the default to be different. The perl6 core dev people state it is possible with a backslash:

cat t.pl
use v6;

class C {
   has Int $.x is rw = 0;

   method foo (Int $i) { $!x += $i; return self; }
   method bar (Int $i) { $!x -= $i; return self; }
   }

C.new()\
 .foo(1)\
 .bar(2)\
 .say;
$ perl6 t.pl
C.new(x => -1)
[download]

But do you want your code to look ugly like that? I do not!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.