Mercurial > libbuf
comparison README.md @ 23:b7690784cd17 0.3.0
misc: update before 0.3.0
author | David Demelier <markand@malikania.fr> |
---|---|
date | Thu, 16 Sep 2021 13:56:31 +0200 |
parents | 7f5b3f035bef |
children | 57c06f7b7d01 |
comparison
equal
deleted
inserted
replaced
22:d87e84936795 | 23:b7690784cd17 |
---|---|
45 | 45 |
46 Also, I wanted a library easy to embed everywhere without a complicated build | 46 Also, I wanted a library easy to embed everywhere without a complicated build |
47 process. This library can be bundled in your project by just copying all .c | 47 process. This library can be bundled in your project by just copying all .c |
48 files and .h files without any modification. | 48 files and .h files without any modification. |
49 | 49 |
50 ### Why every function is defined in its own file? | |
51 | |
52 Because it improves static linking as only symbols you need are bundled into | |
53 your final executable. | |
54 | |
55 ### Why not using `open_memstream`? | 50 ### Why not using `open_memstream`? |
56 | 51 |
57 It's a POSIX function that is not available on every operating system, but if | 52 It's a POSIX function that is not available on every operating system, but if |
58 you don't care about portability you can obviously stick with it. | 53 you don't care about portability you can obviously stick with it. |
59 | 54 |