4.2BSD
4.3BSD-Reno
| 4.2BSD | 4.3BSD-Reno | |
|---|---|---|
| 3 | 1 | |
| 4 | 8 | |
| - | - | |
| 0.0 | 10.0 | |
| 7 months ago | almost 10 years ago | |
| C | C | |
| - | - |
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.
4.2BSD
-
How could the early Unix OS comprise so few lines of code?
Not only early Unix; look at the original inet_addr implementation [0]. It accepts not only "0x" but also just "x" as the 16-base prefix, it doesn't really care about the numbers overflowing, and it parses 09 as equal to 011 (which is decimal 9). And the less said about the coding style, the better.
[0] https://github.com/dank101/4.2BSD/blob/master/lib/libc/inet/...
-
Backward Compatibility, Go 1.21, and Go 2
No need to guess. My man page for inet_aton says it comes from 4.3BSD: https://github.com/dank101/4.3BSD-Reno/blob/master/lib/libc/...
The earlier inet_addr from 4.2BSD has the same logic: https://github.com/dank101/4.2BSD/blob/master/lib/libc/inet/...
inet_aton and inet_addr parses addresses the obvious way. Using something like strtoul or especially sscanf would be stilted. The beauty of C pointers is that it makes simple parsing tasks very easy--perhaps too easy.
-
There is no such thing as a “glibc based alpine image”
It probably made sense in 1983.
https://github.com/dank101/4.2BSD/blob/master/include/netdb....
4.3BSD-Reno
-
Backward Compatibility, Go 1.21, and Go 2
No need to guess. My man page for inet_aton says it comes from 4.3BSD: https://github.com/dank101/4.3BSD-Reno/blob/master/lib/libc/...
The earlier inet_addr from 4.2BSD has the same logic: https://github.com/dank101/4.2BSD/blob/master/lib/libc/inet/...
inet_aton and inet_addr parses addresses the obvious way. Using something like strtoul or especially sscanf would be stilted. The beauty of C pointers is that it makes simple parsing tasks very easy--perhaps too easy.
What are some alternatives?
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
robovm - Ahead of time compiler for JVM bytecode targetting iOS, Mac OSX and Linux
cosmopolitan - build-once run-anywhere c library
proposal - Go Project Design Documents
official-images - Primary source of truth for the Docker "Official Images" program
Codename One - Cross-platform framework for building truly native mobile apps with Java or Kotlin. Write Once Run Anywhere support for iOS, Android, Desktop & Web.