Commit 76e0153d authored by Martin Sustrik's avatar Martin Sustrik

issue 33 - missing virtual destructors

parent d329c55d
...@@ -55,7 +55,9 @@ namespace zmq ...@@ -55,7 +55,9 @@ namespace zmq
zmq_assert (buf); zmq_assert (buf);
} }
inline ~decoder_t () // The destructor doesn't have to be virtual. It is mad virtual
// just to keep ICC and code checking tools from complaining.
inline virtual ~decoder_t ()
{ {
free (buf); free (buf);
} }
......
...@@ -50,6 +50,8 @@ namespace zmq ...@@ -50,6 +50,8 @@ namespace zmq
zmq_assert (buf); zmq_assert (buf);
} }
// The destructor doesn't have to be virtual. It is mad virtual
// just to keep ICC and code checking tools from complaining.
inline ~encoder_t () inline ~encoder_t ()
{ {
free (buf); free (buf);
......
...@@ -35,7 +35,9 @@ namespace zmq ...@@ -35,7 +35,9 @@ namespace zmq
{ {
} }
inline ~yarray_item_t () // The destructor doesn't have to be virtual. It is mad virtual
// just to keep ICC and code checking tools from complaining.
inline virtual ~yarray_item_t ()
{ {
} }
......
...@@ -50,6 +50,12 @@ namespace zmq ...@@ -50,6 +50,12 @@ namespace zmq
c.set (&queue.back ()); c.set (&queue.back ());
} }
// The destructor doesn't have to be virtual. It is mad virtual
// just to keep ICC and code checking tools from complaining.
inline virtual ~ypipe_t ()
{
}
// Following function (write) deliberately copies uninitialised data // Following function (write) deliberately copies uninitialised data
// when used with zmq_msg. Initialising the VSM body for // when used with zmq_msg. Initialising the VSM body for
// non-VSM messages won't be good for performance. // non-VSM messages won't be good for performance.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment