freebsd
libcperciva
| freebsd | libcperciva | |
|---|---|---|
| 6 | 3 | |
| 59 | 111 | |
| - | 0.0% | |
| 0.0 | 7.9 | |
| over 9 years ago | 10 days ago | |
| C | C | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
freebsd
- I cut GTA Online loading times by 70% (2021)
-
Dio deleted the tweet shortly after
Second of all: The horrifying truth is that there is no such thing as a canonical text representation for IPv4 (source) (and yes... I am indeed citing the failed attempt to standardize this as my source for it not being standardized). Authoritatively speaking, all possible (non-binary) representations are equally invalid. In fact, text address resolution is typically delegated to the OS kernel, so what constitutes a "usable" address is liable to vary depending on if you're using Linux, OSX, Windows, or Other.
-
Ask HN: What is the best config file documentation you have seen?
FreeBSD’s config files spring to mind. Here is an example:
https://github.com/lattera/freebsd/blob/master/etc/defaults/...
- Command Line Flags in C++, A Minimalist's Guide
- What is a consensus on 20% free space allocation in pools and keeping that space free? What are real-world performance implications of crossing it?
-
Type-safe generic data structures in C
The macro idea has a long history. It would be good to reference its earlier uses. For example, freebsd/netbsd had "tree.h" back in 2002 [1].
[1] https://github.com/lattera/freebsd/blob/master/sys/sys/tree....
libcperciva
- C Posix complaint argument parsing in 42 loc, inspired by Duff's device
- Type-safe generic data structures in C
-
Compilers Are Hard
On the topic of compilers being hard: In my repositories I'm carrying around a 5 year old workaround (https://github.com/Tarsnap/libcperciva/commit/92e666e59503de...) for a 6 year old bug (https://bugs.llvm.org/show_bug.cgi?id=21183) in clang/LLVM.
You might think that "incorrect code gets generated" would be a maximum-priority must-fix-before-the-next-release bug in a compiler, but apparently not.
What are some alternatives?
glibc - Unofficial mirror of sourceware glibc repository. Updated daily.
stage0 - A set of minimal dependency bootstrap binaries
glibc - GNU Libc
bug - Scala 2 bug reports only. Please, no questions — proper bug reports only.
c_standard_lib - source code of The Standard C Library, by Plauger
ctl - The C Template Library
c4 - C in four functions
ctl - My variant of the C Template Library
Klib - A standalone and lightweight C library
bamboomigrate - bamboomigrate is a typelevel transformation and migration library
swc - Rust-based platform for the Web
pottery - Pottery - A container and algorithm template library in C