Hi all,
Following the blog post about STM, I would like to sollicitate your
attention to come up with some better syntax for the 'transaction'
module.
* First question: 'transaction'. The name is kind of bogus, because
it implies that it must be based on transactional memory. Such a name
doesn'
In a message of Tue, 01 May 2012 11:27:56 +0200, Armin Rigo writes:
>* First question: 'transaction'. The name is kind of bogus, because
>it implies that it must be based on transactional memory. Such a name
>doesn't make sense if, say, you are running the single-core emulator
>version. What the
Hi Laura,
On Tue, May 1, 2012 at 12:03, Laura Creighton wrote:
> So how about 'schedule'?
Might work :-) How about, if we decide to go for a class, the name of
the class? Is it 'schedule.Runner()', 'schedule.Scheduler()', ...? A
concrete instance of this class is no longer stateless, so
'sche
On 1 May 2012 11:03, Laura Creighton wrote:
>
> So how about 'schedule'?
>
> My experience says that if you pick a verb, and not a noun, the code
> often comes out cleaner
Except that this seems particularly ambiguous - it's both a noun and a
verb...
End Bikeshedding.
--
Love regards etc
Dav
Hello,
I contacted you to assist in distributing the money left behind by my late
client,
Regards,
Mr Edward Lee
+60146308549
Fax:+60(0)321784290
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
Hey there,
On Tue, May 1, 2012 at 11:27 AM, Armin Rigo wrote:
> * First question: 'transaction'. The name is kind of bogus, because
> it implies that it must be based on transactional memory. Such a name
> doesn't make sense if, say, you are running the single-core emulator
> version. What the
Re-hi,
Now I did a full circle, and I'm wondering again if we couldn't go
with the single primitive of an "atomic" object. You use it as "with
atomic:", in a way quite traditional for Transactional Memory.
Indeed, it seems after all possible to have the following model: a
pypy-stm interpreter wi
Hi Armin,
On Tue, May 01, 2012 at 15:55 +0200, Armin Rigo wrote:
> Re-hi,
>
> Now I did a full circle, and I'm wondering again if we couldn't go
> with the single primitive of an "atomic" object. You use it as "with
> atomic:", in a way quite traditional for Transactional Memory.
i like this, m
Hi Holger,
On Tue, May 1, 2012 at 16:48, holger krekel wrote:
> Maybe "atomic" could become a __pypy__ builtin and there could be a "ame" or
> so package which atomic-using apps could depend on? In any case,
> I really like the twist of "To remedy the GIL use AME" :)
Yes, indeed, a private name
Armin,
I apologize, I'm only half paying attention, trying to follow along.
What does "ame" stand for? Is there some reason a more descriptive
name isn't used? "Atomic MEmory"? "Armin's Magic Enterprise?"
Thx,
Skip
On Tue, May 1, 2012 at 10:35 AM, Armin Rigo wrote:
> Hi Holger,
>
> On Tue,
Hi,
2012/5/1 Skip Montanaro
> I apologize, I'm only half paying attention, trying to follow along.
> What does "ame" stand for? Is there some reason a more descriptive
> name isn't used? "Atomic MEmory"?
>
"Armin's Magic Enterprise?"
>
Hey, you found the hidden meaning :)
Actually it means
On 05/01/2012 08:35 AM Armin Rigo wrote:
Hi Holger,
On Tue, May 1, 2012 at 16:48, holger krekel wrote:
Maybe "atomic" could become a __pypy__ builtin and there could be a "ame" or
so package which atomic-using apps could depend on? In any case,
I really like the twist of "To remedy the GIL use
12 matches
Mail list logo
