Re:Simple software rasterizer in a single C++11 header file
by ricket on Sunday February 22, 2015 @12:53PM
(#9090192)
I'm not a C++11 developer, I've done a little C++ in the past. What is the pride in putting all the code in the header file? Shouldn't the declarations be there, and the definitions be pulled out into a .cpp file? Is it somehow smaller, faster, more convenient to have it all in a header file?
[ Parent
| on HN ]
Re:Simple software rasterizer in a single C++11 header file
by jgh on Sunday February 22, 2015 @01:07PM
(#9090246)
Header libraries are easier to add to your project because there are no build scripts to figure out or cross-compiling to do or whatever. A lot of Boost is header-only, for example. GLM (OpenGL Mathematics), too, is header-only. OTOH if you end up modifying a header that's included in a whole bunch of places, woe unto you.
Re:Simple software rasterizer in a single C++11 header file
by TheDong on Sunday February 22, 2015 @01:28PM
(#9090354)
The reason Boost is headers only is you have to be a header to be generic. Implementations outside of headers have to friend / otherwise be not truly generic.
Re:Simple software rasterizer in a single C++11 header file
by theyoungestgun on Sunday February 22, 2015 @08:57PM
(#9092154)
Assuming you mean friend in the standard cpp way, that's not exactly correct.
http://stackoverflow.com/questions/495021/why-can-templates-...