From: K. F. <kfr...@gm...> - 2010-06-01 15:28:56
|
Hello Tor - On Tue, Jun 1, 2010 at 5:56 AM, Tor Lillqvist <tm...@ik...> wrote: >> There are other options for portable threads too, such as QThread (from Qt), >> Boost::thread, and OpenMP. > > And I should point out that also GLib has a thread API (which uses the > C library and Win32 APIs on Windows, i.e. no pthreads-win32 involved). > In case you prefer a plain C library... If I understand correctly, GLib is a large framework library that has as part of it a thread api. For my current purposes, I would prefer to stay away from a big framework, and stay close to plain-vanilla C++. (For example, even though I am also working with Qt -- which has a thread api -- my goal here is to do some plain-vanilla, non-Qt multi-threaded programming.) > All this said, unless you are 100% sure you need to write C or C++ > code, why not consider a more modern, garbage collected (as if that > was something modern, hah...), safe, language and environment, Java > and C# being the most obvious choices? On this side note... Oh, I don't need to write C++, rather I prefer to. I find C++ to be the most expressive mainstream language (but, of course, tastes vary). Also, the original java threading model was somewhat naive compared to pthreads, and really didn't gain full functionality until java 5. So I tend to give pthreads (and the win32 api) points for maturity. > ... > --tml Thanks. K. Frank |