RE: Perl6::Doc # Hail to the new pharao

2007-12-30 Thread Conrad Schneiker
Re using perl.com articles in your Perl 6 wiki documentation, were you also planning on adding (links to) Larry Wall's annual "State of the Onion" talks? They contain a wealth of great language design philosophy for people wanting to learn about what sorts of things motivated the exceedingly intere

Re: Multiline comments in Perl6

2007-12-30 Thread Jonathan Lang
Christian Mueller wrote: > i don't know the actually state in the discussion about multiline > comments, but i would propose an idea.. a combination of POD's = and the > traditional route char... Perl 6 already has a robust system for multiline and embedded comments, as described in S02 under "Whi

Re: Multiline comments in Perl6

2007-12-30 Thread Amir E. Aharoni
On 30/12/2007, Jonathan Lang <[EMAIL PROTECTED]> wrote: > The only wart > is that '#( ... )' cannot begin at the very start of a line; but it's > easy enough to get around that restriction - say, with some leading > whitespace. Thanks for the reply - can you please what is the problem with having

Re: Perl6::Doc # Hail to the new pharao

2007-12-30 Thread herbert breunung
first of all thanks to Jonathan Scott Duff, you will be named in the scribes section of the p6doc documentation too and to chromatic: i will name the authors normally like in POD and make a link to perl.com/p6 section in the p6doc where sources of all docs are named. Conrad Schneiker: about o

Re: Multiline comments in Perl6

2007-12-30 Thread Jonathan Lang
Amir E. Aharoni wrote: > On 30/12/2007, Jonathan Lang <[EMAIL PROTECTED]> wrote: > > The only wart > > is that '#( ... )' cannot begin at the very start of a line; but it's > > easy enough to get around that restriction - say, with some leading > > whitespace. > > Thanks for the reply - can you ple

Re: Multiline comments in Perl6

2007-12-30 Thread Offer Kaye
On Dec 30, 2007 6:10 PM, Jonathan Lang wrote: > > Short answer: the compiler has no way of knowing whether the > programmer wants an embedded comment or a line comment; so instead of > guessing, it requires the programmer to disambiguate. > [...snip...] > > # if ($test) > # { > .say; >

Re: Multiline comments in Perl6

2007-12-30 Thread Mark J. Reed
Whitespace is significant in many places. Even in some of the corners of Perl 5. Perl 6 has a different set of rules, and it will take some getting used to, but the rules are designed to let you do things as naturally as possible.This, for instance, works fine: my @values = # (1,2,3) # old

Re: Multiline comments in Perl6

2007-12-30 Thread Jonathan Lang
Offer Kaye wrote: > #( commenting out a large code section, yey for Perl6 multi-line comments... >if ($foo) { > print "...or not :(\n" >} > ) # this should have been the end of the embedded comment ...and since it wasn't, you probably should have chosen other brackets such as: #[

Re: Multiline comments in Perl6

2007-12-30 Thread Christian Mueller
>> Thanks for the reply - can you please what is the problem with having it in the beginning of the line? > > Short answer: the compiler has no way of knowing whether the > programmer wants an embedded comment or a line comment; so instead of guessing, it requires the programmer to disambiguate. >

Re: Multiline comments in Perl6

2007-12-30 Thread Shane Calimlim
On Dec 30, 2007 8:10 AM, Jonathan Lang <[EMAIL PROTECTED]> wrote: > Let's say that the programmer in question wants to comment out all but > the third line; so he prefixes everything else with '#': > > #if ($test) > #{ >.say; > #} else { > # .doit; > #} > > What the writer _wants_ this t