"Actually, be careful(!)" when you talk about things such as "sprites!"

"Sprites," after all, are really 'things' that are 'owned' by a single physical resource: "a video display," and therefore also the entire arcane and perhaps-unknown-to-you shared data structures(!) that are behind-the-scenes involved in managing them.

Therefore, you might easily find yourself running into timing dependencies, race conditions, and other very-unpleasant things which have not been properly considered in your application's parallelism model.

Since we are now are far afield from the initial question re. matrix multiplication, threading, etc., I started a new thread with some questions I have about using those condition variables I'd hesitated considering. Because I was too quick in dismissing the idea.

They work great as far as I am able to get them to work at all.

As far as the 'sprites' go, you'd have to know how they're implemented to make a clear statement about what kind of resource they are, if they are, or to know what timing issues might be at issue.

Since my code is getting them on the screen where they belong, when they belong, without flickering or other troublesome artifacting, I'm satisfied. I've got cycling and all sorts of other things worked out in a thread safe manner. I could include some of the code in my next post to the following thead.

http://www.linuxquestions.org/questi...ry-4175595809/