[Stackless] Question about atomic

Christian Tismer tismer at stackless.com
Thu Jan 8 15:41:21 CET 2004

Tom Locke wrote:

> If, in a function, I do
> a = stackless.atomic()
> Then there will be no autosheduling until the object is destoryed, i.e.
> - at the end of the function
> - if I overwrite the value of 'a' or 'del a'
> Right?


> What about explicit scheduling points?

Nothing at all. This is only about auto stuff.
If your code decides to schedule, it must know what it does.

> If I do a channel send/receive while the atomic is in effect, is that
> ok? Will the sceduler de-schedule me as normal? From my experiments it
> seems the answer is yes.

Sorry? This has nothing to do with auto-scheduling, this
is all explicit, including channels. The auto-stuff is
about preemptive scheduling, which is not officially there, yet.

> What about when I am re-sheduled? Is the atomic status back in effect?

The atomic status is there until it is reset. It is per-tasklet.
Christian Tismer             :^)   <mailto:tismer at stackless.com>
Mission Impossible 5oftware  :     Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a     :    *Starship* http://starship.python.net/
14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34  home +49 30 802 86 56  mobile +49 173 24 18 776
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/

Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list