I''m already using a number of STL containers in my engine, but I was wondering if people thought the priority_queue was worth using for an event queue. Or does it not work too well (for whatever reason) and I should consider writing my own? Each event in the engine has a priority (system, high, medium and low). As an alternative I was thinking of using 1 STL queue container for each queue and just managing priorities myself. Any thoughts? Thanks

I don''t mind using STL for ADTs that I use for holding data that will not be used during the running loop of the engine. (e.g. Texture management, Sprite Management etc) The reason for this I view STL as not Optimized for MY specific need. So i tend to program my own when I use stacks/lists/whatever if they are being used in a realtime environment, but using STL in loading environment and to hold and manage data is fine, but in a realtime situation writing your own can be much better.

In general STL is good but I don''t prefer to use it in a game loop.

I know this may not answer some of the more specific answers on how you should manager your queue, but you know you want that to work better than I.

-Syntax

I think I''ll need it a lot more than 100 times per second.

Thanks