Tom Christiansen wrote:
Exegesis 5 @ http://dev.perl.org/perl6/doc/design/exe/E05.html reads:
# Perl 6
/ < - [A-Za-z] >+ / # All alphabetics except A-Z or a-z
# (i.e. the accented alphabetics)
[Update: Would now need to be <+ - [A..Za..z]> to avoid
Tom Christiansen wrote:
Certainly it's perfectly well known amongst people who deal with
letters--including with the Unicode standard.
"Accent" does have a colloquial meaning that maps correctly,
but sadly that colloquial definition does not correspond to
the technical definition, so in being
FYI, Larry "accents" to "marks" in this commit, as well as some
refactoring of the short adverbs associated with them:
http://www.nntp.perl.org/group/perl.perl6.language/2010/05/msg33671.html
Thanks,
Moritz
--- Forwarded message ---
From: nigelsande...@btconnect.com
To: "Dave Whipp - dave_wh...@yahoo.com"
<+nntp+browseruk+2dcf7cf254.dave_whipp#yahoo@spamgourmet.com>, "Dave
Whipp - d...@whipp.name"
<+nntp+browseruk+e66dbbe0cf.dave#whipp.n...@spamgourmet.com>
Cc:
Subject: Re: Paral
--- Forwarded message ---
From: nigelsande...@btconnect.com
To: "Dave Whipp - d...@whipp.name"
<+nntp+browseruk+e66dbbe0cf.dave#whipp.n...@spamgourmet.com>
Cc:
Subject: Re: Parallelism and Concurrency was Re: Ideas for
a"Object-Belongs-to-Thread" (nntp: message 4 of 20) threading mo
Em Dom, 2010-05-16 às 19:34 +0100, nigelsande...@btconnect.com escreveu:
> 3) The tough-y: Closed-over variables.
> These are tough because it exposes lexicals to sharing, but they are so
> natural to use, it is hard to suggest banning their use in concurrent
> routines.
This is the point
Em Dom, 2010-05-16 às 19:34 +0100, nigelsande...@btconnect.com escreveu:
> Interoperability with Perl 5 and
> is reference counting should not be a high priority in the decision making
> process for defining the Perl 6 concurrency model.
If we drop that requirement then we can simply go to the
On Tue, 18 May 2010 11:39:04 +0100, Daniel Ruoso wrote:
This is the point I was trying to address, actually. Having *only*
explicitly shared variables makes it very cumbersome to write threaded
code, specially because explicitly shared variables have a lot of
restrictions on what they can be (t
On Tue, 18 May 2010 11:41:08 +0100, Daniel Ruoso wrote:
Em Dom, 2010-05-16 às 19:34 +0100, nigelsande...@btconnect.com escreveu:
Interoperability with Perl 5 and
is reference counting should not be a high priority in the decision
making
process for defining the Perl 6 concurrency model.
I
"So there me was beating boulder into powder because me couldn't eat it,
and magic ball land in lap. Naturally me think, "All right, free egg." because
me stupid and me caveman. So me spent about three days humping and bust open
with thigh bone so me could eat it good. Then magic ball shoot Oog wit
Em Ter, 2010-05-18 às 15:15 +0100, nigelsande...@btconnect.com escreveu:
> > 1) the interpreter doesn't need to detect the closed over variables, so
> > even string eval'ed access to such variables would work (which is, imho,
> > a good thing)
> You'd have to explain further for me to understand wh
On Tue, May 18, 2010 at 3:19 AM, wrote:
> The guts of the discussion has been kernel threading (and mutable shared
> state) is necessary. The perception being that by using user-threading (on
> a single core at a time), you avoid the need for and complexities of
> locking and synchronisation. And
Em Ter, 2010-05-18 às 12:58 -0700, Alex Elsayed escreveu:
> You are imposing a false dichotomy here. Neither 'green' threads nor kernel
> threads preclude each other. In fact, it can be convincingly argued that they
> work _best_ when combined. Please look at the GSoC proposal for hybrid
> threadi
13 matches
Mail list logo
