提交 30f9a818 编写于 作者: Y youngwolf

Explicitly use std::list.

上级 e6e79061
......@@ -322,7 +322,7 @@ private:
//we must guarantee these objects not be freed from the heap or reused, so we move these objects from object_can to invalid_object_can, and free them
//from the heap or reuse them in the near future. if ASCS_CLEAR_OBJECT_INTERVAL been defined, clear_obsoleted_object() will be invoked automatically and
//periodically to move all invalid objects into invalid_object_can.
list<object_type> invalid_object_can;
std::list<object_type> invalid_object_can;
std::mutex invalid_object_can_mutex;
};
......
......@@ -187,7 +187,7 @@ protected:
//msg_can contains messages that were failed to send and tcp::socket_base will not hold them any more, if you want to re-send them in the future,
// you must take over them and re-send (at any time) them via direct_send_msg.
//DO NOT hold msg_can for future using, just swap its content with your own container in this virtual function.
virtual void on_send_error(const asio::error_code& ec, list<typename super::in_msg>& msg_can) {unified_out::error_out("send msg error (%d %s)", ec.value(), ec.message().data());}
virtual void on_send_error(const asio::error_code& ec, std::list<typename super::in_msg>& msg_can) {unified_out::error_out("send msg error (%d %s)", ec.value(), ec.message().data());}
virtual void on_close()
{
......@@ -389,7 +389,7 @@ private:
#endif
std::shared_ptr<i_unpacker<out_msg_type>> unpacker_;
list<typename super::in_msg> last_send_msg;
std::list<typename super::in_msg> last_send_msg;
asio::io_context::strand strand;
};
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册