From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8dde30c2da13284a
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!u30g2000hsc.googlegroups.com!not-for-mail
From: Lucretia <lucretia9@lycos.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: Is Parallel Programming Just Too Hard?
Date: 29 May 2007 11:33:00 -0700
Organization: http://groups.google.com
Message-ID: <1180463580.595241.43420@u30g2000hsc.googlegroups.com>
References: <84335240.OblkFGBlpY@linux1.krischik.com>
NNTP-Posting-Host: 62.56.125.216
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1180463588 31410 127.0.0.1 (29 May 2007 18:33:08
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 29 May 2007 18:33:08 +0000 (UTC)
In-Reply-To: <84335240.OblkFGBlpY@linux1.krischik.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Opera/9.10 (X11; Linux i686; U; en),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: u30g2000hsc.googlegroups.com; posting-host=62.56.125.216;
   posting-account=G-J9fgwAAADgpzBiEyy5tO4f8MX5fbpw
Xref: g2news1.google.com comp.lang.ada:15971
Date: 2007-05-29T11:33:00-07:00
List-Id: <comp.lang.ada>

On May 29, 8:29 am, Martin Krischik <krisc...@users.sourceforge.net>
wrote:
> Hi,
>
> http://developers.slashdot.org/article.pl?sid=07/05/29/0058246

Interesting how it mentions games programmers, having worked in that
industry, I know that games programmers just can't get to grips with
threading/tasking, it is just too hard for them. (Un)fortunately, it's
something that needs to be resolved.

When I started working, where I worked, I added a mouse cursor routine
on a thread, got it working nicely too (considering), and was asked if
it could be turned off in debug build, because when the debugger
kicked it, it didn't always go the correct place (maybe my fault, I
don't know, I'm not that experienced with threads). I just told them,
no. The code didn't stay too long, as the main game was on a (very
heavy) loop and hogged the cpu, the mouse ended up in the loop.

And, yes, they are thick.

Luke.