[Thread-SIG] Re: [Python-Dev] Re: marking shared-ness

[Sean Jensen_Grey]

http://www.cs.bris.ac.uk/~alan/javapp.html

Take a look at the above link. It merges the Occam model with Java and uses
'channel based' interfaces (not sure exactly what this is). 

But they seem pretty exicted.

I vote for using InterlockedInc/Dec as it is available as an assembly
instruction on almost everyplatform. Could be then derive all other locking
schemantics from this?

And our portability problem is solved if it comes in the box with gcc.

On Fri, 21 Apr 2000, Sean Jensen_Grey wrote:

> > > Since Python has nothing really private, this implies in
> > > fact to protect every single object for free threading,
> > > although nobody wants this in the first place to happen.
> > 
> > How does Java solve this problem?  (Is this analagous to native vs. green
> > threads?)
> > 
> > > Python is not designed for that. Why do you want to enforce
> > > the impossible, letting every object pay a high penalty
> > > to become completely thread-safe?
> > 
> > Hmm, how about declaring only certain builtins as free-thread safe?  Or is
> > "the impossible" necessary because of the nature of incref/decref?
> 
> http://www.javacats.com/US/articles/MultiThreading.html
> 
> I would like
> 
> sync foo:
>         bloc of code here
> 
> maybe we could merge in some Occam while were at it. B^)
> 
> 
> sync would be a most excellent operator in python.
> 
> 
> 
> 
> _______________________________________________
> Thread-SIG maillist  -  Thread-SIG@python.org
> http://www.python.org/mailman/listinfo/thread-sig
>