std containers and pointers

[cpisz]

I am going to make a queue of events to be dispatched to 1 or many
event handlers. I know I read that in order to use a std container I
must implement a default constructor, a copy constructor, and an
assignment operator. However, do any of these apply if I only queue up
pointers to events and then release the allocated memory after the
event has been dispatched and processed? And is that a bad idea?

[Alf P. Steinbach]

* cp***@austin.rr.com:

I am going to make a queue of events to be dispatched to 1 or many
event handlers. I know I read that in order to use a std container I
must implement a default constructor, a copy constructor, and an
assignment operator.

The requirements are copy constructible and assignable, not default
constructible.

However, do any of these apply if I only queue up
pointers to events and then release the allocated memory after the
event has been dispatched and processed?

Pointers can be copied and assigned, so they fill the requirements.

And is that a bad idea?

Raw pointers is generally a bad idea, especially for novices. Use some
smart pointer. boost::shared_ptr comes to mind; check out the Boost
library.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?