I would like to write code in .hpp without separation to .h and .cpp I did it. I use .cpp only for static class-fields definitions
Obviously template libraries need to be header only, but 开发者_开发技巧for non-templates, when should you make things header-only?If you think your non-template library could be header-only, consider
I\'m trying to write a header-only library of helper functions for myself. (I\'m using boost and SDL, and boost is much easier to use, so I want to emulate that for my own helper library.)
It seems like I had to inline quite a bit of code here. I\'m wondering if it\'s bad design practice to leave this entirely in a header file like this:
I\'d like to package a library I\'m working on as a header-only library to make it easier for clients to use. (It\'s small and there\'s really no reason to put it into a separate translation unit开发者
加载中,请稍侯......