
21 Mar
2010
21 Mar
'10
6:48 p.m.
Artyom wrote:
Why? I give you a simple example: one of the pearls of Boost: Boost.Asio is one of most painful libraries to use. [because it is header-only]
I believe asio is header-only because the author finds that more practical to use and deploy. It is him you should try to convince otherwise.
Result (liked executable size with gcc-4.3):
Build Size (-Os stripped) Asio: 245K Pimpl: 190K
Could you try this while whole program optimization (gcc 4.5+) turned on and tell me whether there is still a difference?