Re: multithreading best practice

From	Michael Uplawski <michael.uplawski@uplawski.eu>
Newsgroups	comp.lang.ruby
Subject	Re: multithreading best practice
Date	2015-01-13 09:03 +0100
Organization	news.babsi.de for open-news-network.org
Message-ID	<slrnmb9ka8.256.michael.uplawski@drusus.uplawski.eu> (permalink)
References	<slrnmb58gv.2co.michael.uplawski@drusus.uplawski.eu> <chfodbF9mc9U1@mid.individual.net> <slrnmb5fnu.2c5.michael.uplawski@drusus.uplawski.eu> <chg9qhFehsuU1@mid.individual.net>

Show all headers | View raw

On Sun, 11 Jan 2015 22:55:29 +0100,
Robert Klemme <shortcutter@googlemail.com> wrote:
> No.  All threads that want to access the size must go through the mutex:
> https://gist.github.com/rklemme/10f36380ab5899911b5d

Okay. The crucial part is the mandatory check for the identity of the
thread which is currently in hold of the mutex. Thank you for the nice
code-example!

Looks like a pattern that I have not yet been confronted to. And I
frequently encounter difficulties, when threads are wrapped in objects.
Although I have much appreciated this possibility and am familiar with
different thread classes (from Qt, Java and some project-specific), they
stay elements of procedural programming in my head...

Thanks for piercing another hole into my limited horizon... ;-)

Cheerio,

Michael, -I am NOT Charlie-, Uplawski

>
> Cheers
>
> 	robert
>
>
>

-- 
GnuPG/OpenPGP  4096R/3216CF02 2013-11-15 [expires: 2015-11-15]
sub   4096R/2751C550 2013-11-15 [expires: 2015-11-15]

Back to comp.lang.ruby | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

multithreading best practice Michael Uplawski <michael.uplawski@uplawski.eu> - 2015-01-11 17:17 +0100
  Re: multithreading best practice Robert Klemme <shortcutter@googlemail.com> - 2015-01-11 17:58 +0100
    Re: multithreading best practice Robert Klemme <shortcutter@googlemail.com> - 2015-01-11 18:02 +0100
      Re: multithreading best practice Michael Uplawski <michael.uplawski@uplawski.eu> - 2015-01-11 19:22 +0100
    Re: multithreading best practice Michael Uplawski <michael.uplawski@uplawski.eu> - 2015-01-11 19:20 +0100
      Re: multithreading best practice Robert Klemme <shortcutter@googlemail.com> - 2015-01-11 22:55 +0100
        Re: multithreading best practice Michael Uplawski <michael.uplawski@uplawski.eu> - 2015-01-13 09:03 +0100
          Re: multithreading best practice Robert Klemme <shortcutter@googlemail.com> - 2015-01-14 22:37 +0100
            [OT] Response to Robert Klemme [Was: multithreading best practice] Michael Uplawski <michael.uplawski@uplawski.eu> - 2015-01-15 13:32 +0100

csiph-web