On Tue, Apr 28, 2009 at 03:08:05PM -0400, Mark J. Reed wrote:
> On Tue, Apr 28, 2009 at 2:27 PM, Patrick R. Michaud
> wrote:
> > * The Unicode character name database [2] has parens in the
> > name property field for many characters
> >
> > 000A;;Cc;0;B;N;LINE FEED (LF)
>
> That's no
On Tue, Apr 28, 2009 at 2:27 PM, Patrick R. Michaud wrote:
>> According to the 5.0.0 standard, section 4.8:
>>
>> "Unicode character names contain only uppercase Latin letters A
>> through Z, digits, space, and hyphen-minus."
>>
>> So it seems the notes in parentheses are not considered part of th
On Tue, Apr 28, 2009 at 07:22:18AM -0700, Larry Wall wrote:
> On Mon, Apr 27, 2009 at 11:04:03AM +0200, Helmut Wollmersdorfer wrote:
> > Std.pm allows e.g.
> >
> > "\x[ 41 , 42 , 43 ]"
> >
> > For convenience - especially with long charnames - it should be possible
> > to write
> >
> >
On Tue, Apr 28, 2009 at 01:28:40PM -0400, Mark J. Reed wrote:
> On Tue, Apr 28, 2009 at 10:22 AM, Larry Wall wrote:
> > Does anyone know offhand whether the Unicode Consortium has an explicit
> > policy against use of punctuation in a charname? So far they only
> > seem to use hyphen and parens,
On Tue, Apr 28, 2009 at 10:22 AM, Larry Wall wrote:
> Does anyone know offhand whether the Unicode Consortium has an explicit
> policy against use of punctuation in a charname? So far they only
> seem to use hyphen and parens, but I wonder to what extent we can
> depend on that...
>
According to
On Mon, Apr 27, 2009 at 11:04:03AM +0200, Helmut Wollmersdorfer wrote:
> It's not explicitly specified, if insignificant whitespace is allowed in
> \c[...], \x[...], etc.
>
> Std.pm allows e.g.
>
> "\x[ 41 , 42 , 43 ]"
>
> For convenience - especially with long charnames - it should be
On Thu, Aug 04, 2005 at 09:29:21PM +0400, Andrew Shitov wrote:
: in fact, that is exactly
:
: (print.getArgument(3) * 3); the same as above.
:
: so why not 'print($x)' == 'print ($x)' ;-)
Because most people's expectations diverge from yours, actually, and
we got tired of answering the FAQ.
print (1+2)*3;
can print 9, instead of 3.
I'd prefer always have '3' (as a result of sum 1 + 2) here.
A C-programmer would tread this like
(print (1 + 2) * 3); # prints int, then returns void
print (or do)? And is
print .(1+2)*3
allowed?
in fact, that is exactly
(print.g
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
13 matches
Mail list logo
