Subj : Re: VC++ 2005 beta1 fails with pthreads benchmark tests
To   : comp.os.ms-windows.programmer.nt.kernel-mode,comp.programming.threads
From : Maxim S. Shatskih
Date : Wed Apr 20 2005 06:31 am

> source code of the library they use. The threading functions of MS
> are in my eyes a nightmare. There is no concept behind it since
> there are so many incompatible function calls to start a thread, for example:
> _beginthread, beginthreadex, CreateThread, AfxBeginThread, ...

CreateThread is a low-level OS API. The Win32.

_beginthreadex is a C runtime function must be used to allow some nasty CRT
functions ( like asctime() ) to work. A wrapper around CreateThread. Not an OS
function.

AfxBeginThread is a part of the MFC toolkit. A wrapper around CreateThread. Not
an OS function.

The Win32 routines are very well-designed. Compared to POSIX threads with a
brain damaged concept of "condvar" it is really better. Well, Win32 event can
be emulated in POSIX too by using a semaphore with count 1.

> ... and each with its own thread proc format and limitations and/or
> differences...  It simply is yelling for a standard.

Win32 is the only standard most people really care, for UI apps especially.

> version, and code correctness. Ie. wheter the VC++2005 compiler

BTW - is Whidbey a released product? or a beta?

> It seems to me that VC++2005 is a complete new design, and not building
> on the VC++6 design.

Not sure about the C/C++ compiler part. MS always shipped one of the build
versions of their internal C++ compiler (used to build Windows, Office etc) as
the compiler for Visual C++.

-- 
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

.