Subj : Re: Study Material for Multi-threaded application developement in To : comp.programming.threads From : Torsten Robitzki Date : Sat May 28 2005 12:08 pm Hi Arash, first of all the expression "advertise" was not meant to insult you. So I'm sorry if you got it that way. partow@gmail.com wrote: > Hi Torsten, > > The reason why there are different error handling techniques is > because the user may need either the an exception oriented mechanism > (where exceptions are thrown) or they may have a logging environment, > where failures will be logged and tracked/intercepted term here>. Yes, I've got that but what I was talking about is, that you have that choice for the normal mutex, but not for the rw-mutex. To make such a wrapper more valuable from a users perspective I would add two error handling policies , one for usual runtime errors and one for error that can not happen (aka bugs). For my usual application, I can't see any reason to not handle errors by exceptions / asserts. But that might be personal preferences ;-) > Overall the class is meant to show how the pthreads API can be used > within a C++ context. and as mentioned before the site which was > linked to in my so-called *advertisement* mentions that libraries such > as ACE and BOOST should be considered as being more advanced and more > functional and that the wrappers are by mere "educational" - learning > tools/aids Ok, I have to admit that I just had a quick glance over your pages and thus reported here, what (in my opinion) have to be fixed to make that library more usable. And I'm sure that a thin C++ wrapper for pthread can be of great value if done properly. > If you like have a quick look at this library: > http://www.partow.net/downloads/producer-consumer-source.zip I will try to have a look at that latter this weekend, regards Torsten .