Search Results for "mutex"

cocoyaxi (co for short), is an elegant and efficient cross-platform C++ base library. It contains a series of high-quality base components, such as a go-style coroutine, coroutine-based network programming framework, command line, and config file parser, high-performance log library, unit testing framework, JSON library, etc. co has implemented a go-style coroutine, which has the following features. Multi-thread scheduling, the default number of threads is the number of system CPU cores....

Libthreadar is a C++ library providing an abstracted set of C++ *classes* to manipulate threads in a very simple and efficient way from your C++ code. It also handles exceptions thrown from a thread and propagated to another one, when the later is calling the thread::join() method. This let one manage exceptions as simply as it is in C++ single threaded context. Additionally, all the related objects around multi-threading (mutex, semaphore, ...) are provided, under easy to use...

... and chronological order. Use malloc{slower-but-easy} or fix (static) memory. - OAList01: Object-Kind of a predefined pre-reserved List with X Elements (with constant user-data size), with secur modify functions and option to use locks (POSIX: mutex). Supporting a BusyList and a IdleList for easy build of e.g. a FIFO without need of much time for mem-allocation. - Release-Notes see uws-Lnkdlst-readme.txt in the tar.gz file(s) and in „Files“.

The ulttiny library is small, easy to use and very fast. It's optimized especially for scenarios where tasks and task groups are dynamically and concurrently created on the fly.

A Ring-Buffer instance could be used with element types - char - long - long long - void* . Focus is on a hardened SW structure with buffer-instance-pointer check (not very fast but more secure). Some features are globally choosable on compile-time (e.g. switch multithread support off completely to have faster access). Note: User Interface is for Test and Tutor Code only.

A cross-platform implementation of a mutex, that automatically checks for everything, you might be doing wrong: - DeadLocks - Invalid mutex leave order - Thread Shutdown, while still holding mutex locks - Destroying a locked mutex - (Un)Locking a destroyed mutex - UnLocking an unlocked mutex - UnLocking an mutex locked by another thread - Locking a non-recursive, locked mutex - Not destroying all mutexes before application termination Every abnormal produces a console output...

A set of C++ basic modules, which can be used for C++ Training or some small projects