Limit number of running threads with NewNamedSemaphore and GetSemaphore example

[CarlBarnes]

If the Semaphore only needs visibility inside the one EXE it does NOT need a Name so you could use NewSemaphore(LONG initial=0,LONG max=1). That way you have no possible name issues and the OS does not need to manage your named object.

You could probably do this simpler with a Global Long protected by a Critical Section, or Vista added the Slim Reader Write lock.

@elankreijer

This version is designed to limit the number of threads per process (inside a application).

I was thinking of your other post:

Limit number of running applications with NewNamedSemaphore example

To limit the number of running application, this code can be used. In this example the limit will by set by a value set in the database, the limiting has to be done after open files. Please not that some templates and derived WindowManager classes don’t like being terminated by RETURN LEVEL:Notify from the Init() method. Semaphore names must be unique, they share a system wide namespace. Inside application Main (Frame) procedure: #AT Local Data \ Generated Declarations AppLock &I…