31 Aug
2005
31 Aug
'05
11:15 p.m.
Hi Rob, --- Rob Stewart <stewart@sig.com> wrote:
I'd say that unless you know that using virtual functions causes problems, you shouldn't presume that they do. If users say the library is too big and this technique significantly affects the size, then it may be worth considering at that time.
As I said in another reply, I did find a need to do this change to eliminate code bloat with several compilers. As an example, Borland C++ 5.6.4 seems to add approximately 100 bytes to the executable for each asynchronous call if a virtual function is used in win_iocp_operation. As the change didn't impact the public interface of asio, it seemed like a win. Cheers, Chris