I was reading Synopsis 4 with regards to multi core programming. It
seems to be infused with a bias towards non-parallel models of
computation. Concurrently appears to be an add-on feature -- whereas we
should have a mindset that explicit sequential constraints are the
add-on feature.
Two sta
Jonathan Lang wrote:
> How about '~#', meaning something along the lines of "string-like
> comment"? The idea is that the syntax that follows this would conform
> closely to that of string literals (i.e., quotes). We might even
> consider loosening the restrictions on delimiter characters, allowi
I've been putting a fair amount of thought into this. Here's what
I've come up with:
Perl 6 has several instances where whitespace is required or forbidden
in order to better facilitate "Do What I Mean" programming: for
instance, by having the presence or absence of whitespace before curly
braces
Author: larry
Date: Wed Jan 2 11:30:16 2008
New Revision: 14478
Modified:
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S06.pod
Log:
Rationalize migration strategy from Perl 5 to Perl 6 using transitional p5=>
operator
Modified: doc/trunk/design/syn/S03.pod
=
Paul Hodges wrote:
> http://perl6.org/doc/design/syn/S02.html still says:
> "Intra-line comments will not be supported in standard Perl"
This is wrong, since S02 also defines intra-line comments, under
"Whitespace and Comments". It calls them 'embedded comments'. You
don't need a 'use' statemen
I love this list. I wish I had more of value to contribute. =o]
But for those of you who don't want to read a long blather, this is
mostly opinion, hopefully sans soapbox. Feel free to skip to the end.
> What's with the sudden influx of people swooping in at the
> last minute and attacking design
