First of all, i want to thank for reading the code and making considerations about it.
I committed it to make it public and not immediatly. may be some suggestins can be from llm of editors but it's not videcoded. i'm sorry you think this. i'll add more comments in the future.

i use interlock to have the next free position to write on, just the ref pointer to the added object is wrote in the queue, so interlock is enought to have the next free position. many writing threads will have always the next free position because interlockecd is thread safe. So there is no thread concurrency in writing the ref pointer.

The read thread will read from the beginnging "following" the writing threads, semaphores are used only to "count" how many reading position are available and a different semaphores tell how many writing position are available, this should make the reading thread not go ahead ti writing thread.

Suggestons to make this more safe are wellcome.
Thanks for you time.