Httpserver.h: Single header library for writing non-blocking HTTP servers in C

Re:Httpserver.h: Single header library for writing non-block... by mnutt on Thursday December 12, 2019 @07:14PM (#21777943)

To elaborate on the other responses, “single-header” means “one-line import into your project”, and since c doesn’t have a standard module system, the alternative means hooking up the library’s module system to yours, or otherwise separately building and linking it to your project.

[ Parent | on HN ]

Re:Httpserver.h: Single header library for writing non-block... by danellis on Thursday December 12, 2019 @08:31PM (#21778358)

> the alternative means hooking up the library’s module system to yours

What "module system"? The alternative would be one .c file and one .h file. It's negligible effort to add these to any project that already has more than one .c file.

[ Parent | on HN ]

Re:Httpserver.h: Single header library for writing non-block... by mnutt on Thursday December 12, 2019 @10:07PM (#21778831)

I meant build system, such as cmake. I assume the alternative to a single-header library would be lots of .c and .h files, and something to build them into a dynamically-linked library. The alternative, just dumping them into your project, means that once you get into .c files you typically have to start enumerating those somewhere in your own build system, rather than just including them from one of your own headers.

[ Parent | on HN ]

Re:Httpserver.h: Single header library for writing non-block... by vnorilo on Thursday December 12, 2019 @11:50PM (#21779211)

Besides, even for a single translation unit (such as a quick hello world) you could just #include the .c file to avoid setting up a makefile.

[ Parent | on HN ]