Iβm not fully sure what the intent of the joke is, but note that yes, itβs true that a header typically just has the prototype. However, tons of more advanced libraries are βheader-onlyβ. Everything is in a single header originally, in development, or itβs a collection of headers (that optionally gets βamalgamatedβ as a single header). This is sometimes done intentionally to simplify integration of the library (βjust copy this files to your repo, or add it as a submoduleβ), but sometimes itβs entirely necessary because the code is just template code that needs to be in a header.
C++ 20 adds modules, and the situation is a bit more involved, but Iβm not confident enough of elaborating on this. :) Compile times are much better, but itβs something that the build system and the compilers needs to support.
Iβm not fully sure what the intent of the joke is, but note that yes, itβs true that a header typically just has the prototype. However, tons of more advanced libraries are βheader-onlyβ. Everything is in a single header originally, in development, or itβs a collection of headers (that optionally gets βamalgamatedβ as a single header). This is sometimes done intentionally to simplify integration of the library (βjust copy this files to your repo, or add it as a submoduleβ), but sometimes itβs entirely necessary because the code is just template code that needs to be in a header.
C++ 20 adds modules, and the situation is a bit more involved, but Iβm not confident enough of elaborating on this. :) Compile times are much better, but itβs something that the build system and the compilers needs to support.
Thanks. I didnβt know about these advanced libraries, and had not heard of C++ modules either. Appreciate the explanation.