Hacker News Reader

What is the significance of a library being "header-only"?

C headers can include arbitrary code, right? So why is "header-only" better than having file.h & file.c?

Why would I want to deal with downloading and handling multiple files when I can just use a single file?

Turning a header-only library into file.h and file.c is easy if I want to do it. Turning a multi-file project into a single header file is a lot more work.

A "header-only" library can presumably be multiple header files, which is not what you are discussing.

Why not say what you really mean? Which seems to be: "single-file" library.

Reply on news.ycombinator.com