On Thu, 4 Aug 2005 20:21:18 +0800, Autrijus Tang <[EMAIL PROTECTED]>
wrote:
> On Thu, Aug 04, 2005 at 10:55:12AM +0400, Andrew Shitov wrote:
> > why do we have to give up a space when calling functions under Pugs?
> >
> > A need to type open('file.txt') instead of open ('file.txt') makes
> > me p
I've just realised I quoted the wrong doc earlier, I meant to link to:
http://dev.perl.org/perl6/doc/design/syn/S12.html#Methods
.doit ()# ILLEGAL (two terms in a row)
.doit .() # okay, no arguments, same as .doit()
I had wrongly thought this also applied to subroutine calls, and th
Thus spake Autrijus:
This is so:
print (1+2)*3;
can print 9, instead of 3.
Just a newbie question: what would
print (1+2)x3;
print (or do)? And is
print .(1+2)*3
allowed?
brano tichý
On Thu, Aug 04, 2005 at 10:55:12AM +0400, Andrew Shitov wrote:
> why do we have to give up a space when calling functions under Pugs?
>
> A need to type open('file.txt') instead of open ('file.txt') makes
> me perplexing (not perl-flexing ;-) Our recent discussions in 'zip with()'
> gave no answer
> why do we have to give up a space when calling functions under Pugs?
>
> A need to type open('file.txt') instead of open ('file.txt') makes
> me perplexing (not perl-flexing ;-) Our recent discussions in 'zip with()'
> gave no answer.
Not sure whether it's enough of an answer, but see:
http://d
