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
--- 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
aObject-Belongs-to-Thread (nntp: message 4 of 20) threading model
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 I
On Tue, 18 May 2010 11:39:04 +0100, Daniel Ruoso dan...@ruoso.com 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
On Tue, 18 May 2010 11:41:08 +0100, Daniel Ruoso dan...@ruoso.com 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
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 with
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
threading
