@rayman22201 for my very specific case (softtimerpool) the tickthread needs to sleep (after doing the counting-,signalling- and api-handling-stuff) to obtain the user-defined timebase for the artificial ticks and I don´t like a thread for each counter (that would be resource-burning . My solution should also run within resource-limited environments (tinyavr for instance).
@mashingan yes thanks for your hint; I looked at it but thats not multi-threaded. It runs inside the same thread(polling) - it`s for asynchronous I/O. I need a own thread to obtain the artificial ticks. Its not for critical timing purposes; often protocols need that (tcp/ip for instance) or for dimming LED´s and so on.
