threading ever?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

threading ever?

Raoul Duke
hi, some day will threading be more prevalent than just neko? android
already requires it, it seems. there are so many issues with it. just
look at the history of concurrency issues in java. understanding e.g.
when an object is actually visible to another object, when it is
defined vs. when there is slop and you might get a null when you
thought you had actually set a value, yadda... how is that all to be
taken care of at the haxe level?? thanks.

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: threading ever?

Nicolas Cannasse
Le 23/09/2011 00:01, Raoul Duke a écrit :
> hi, some day will threading be more prevalent than just neko? android
> already requires it, it seems. there are so many issues with it. just
> look at the history of concurrency issues in java. understanding e.g.
> when an object is actually visible to another object, when it is
> defined vs. when there is slop and you might get a null when you
> thought you had actually set a value, yadda... how is that all to be
> taken care of at the haxe level?? thanks.

There is one good model for concurrency that does not require specific
language features which is called the "actor model". It comes from
Erlang but is also implemented in Scala for instance. It can be easily
built on top of low-level MT constructs such as mutexes and dequeues.

Best,
Nicolas

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: threading ever?

laurence taylor
In reply to this post by Raoul Duke

There is an interface for actors in Stax, if you're interested.
regards,
Laurence

> hi, some day will threading be more prevalent than just neko? android
> already requires it, it seems. there are so many issues with it. just
> look at the history of concurrency issues in java. understanding e.g.
> when an object is actually visible to another object, when it is
> defined vs. when there is slop and you might get a null when you
> thought you had actually set a value, yadda... how is that all to be
> taken care of at the haxe level?? thanks.
>
> --
> haXe - an open source web programming language
> http://haxe.org

--
haXe - an open source web programming language
http://haxe.org