optparse
rust-base64
Our great sponsors
optparse | rust-base64 | |
---|---|---|
5 | 9 | |
314 | 572 | |
- | - | |
0.0 | 7.5 | |
6 months ago | about 1 month ago | |
C | Rust | |
The Unlicense | Apache License 2.0 |
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.
optparse
-
Porting my very simple C code from Unixen/macOS to Windows
Between -std=c99 and removing these headers, you're missing time definitions (struct timeval, gettimeofday) and option parsing definitions (struct option, getopt_long). Mingw-w64 provides all this for compatibility, but MSVC has none of these, so you'll need to write replacements. I've written embeddable, public domain implementations of getopt and something like getopt_long, in case that helps. These are how I deal with option parsing portability.
-
How to properly handle position non-specific program arguments? ./my_prog --format:"mp3"
getopt_long is a GNU extension, common across unix-like systems, for parsing long options. You can find libraries for functionality as well.
-
How to make programs for linux
When I need something more sophisticated, where long options would be nice, I reach for my own Optparse.
-
[ Feed back wanted ] Is this a good way to handle lot of if instead of if else?
https://github.com/skeeto/optparse (short and long)
-
Debian discusses vendoring again
This is bug-free and feature complete so it never needs to be updated. When I need argument parsing in a C program, I just copy-paste that into my source and massage it into place. Sometimes I cut the fprintf() stuff, or replace the isalnum, or otherwise adapt it to fit the program's needs. The point is that it becomes wholly owned by the project using it. It's a similar story for long option parsing.
rust-base64
- Rust is not the language for you if you don't like traits
-
Base64 Implementation in Rust
It would be interesting to compare your implementation and the most popular implementation for Rust+base64: https://github.com/marshallpierce/rust-base64
- Rust-base64: restore {encode, decode} convenience functions
-
Question in Rust about Base64 encoding for xmlrpc
I am writing a CLI util in rust that utilizes xml-rpc-rs to talk to an rtorrent server and I would like to be able to add torrent files. OK according to the python implementation, which some of the rtorrent developers have said is good, of xmlrpc-client it uses this base64 format: https://datatracker.ietf.org/doc/html/rfc2045.html#section-6.8 I base64 encode /some/file/foo.torrent and send it up. OK!
-
Announcing uuid-simd, hex-simd and base64-simd!
Funny that you claim base64 forbids unsafe code while linking a PR where the current maintainer of the crate explicitly agrees that unsafe for the purpose of SIMD-acceleration is a-okay. Did you by any chance meant to link https://github.com/marshallpierce/rust-base64/pull/114 instead? ;)
-
Fast Rust Builds
> It does need to be in the standard library
When I say that something “has to be in the standard library”, I mean that it can’t be implemented outside the standard library. That’s certainly not the case here. You’re using an outright bad definition of “need” here—subjective opinion rather than objective requirement.
> because everyone needs it
This is factually wildly wrong. I wrote a fair bit more here but decided it wasn’t helpful. Précis: web stuff tends to load it indirectly (though amusingly most of the time actually not use it, so that Base64 code won’t actually end up in your binary), but it’s not terribly common outside of internet stuff to reach for Base64.
I’ll leave just one more remark about Base64: once things are in the standard library, breaking changes can no longer be made; the base64 crate is still experiencing breaking changes (<https://github.com/marshallpierce/rust-base64/blob/master/RE...>, 0.12 and 0.13 were last year and 0.20 is not released), largely for performance reasons.
Please don’t just call the thin-std approach “problematic” without acknowledging that the alternative is at least as problematic, just with a different set of caveats.
-
Stable versions of most important community crates
Many of these have their own tracking issues on the path to v1.0. For example see this one for base64.
-
Debian discusses vendoring again
I see base64. If the standard library has base64 encoding, go ahead and use it. But as a third-party dependency? Again, base64 encoding and decoding is trivial. I've written this a few times myself. It's not worth a dependency.
What are some alternatives?
getopt - POSIX getopt() as a portable header library
unicode-xid
perl5 - 🐪 The Perl programming language
itoa - Fast integer to ascii / integer to string conversion
rust-fnv - Fowler–Noll–Vo hash function
portable-simd - The testing ground for the future of portable SIMD in Rust
ulid-rs - This is a Rust implementation of the ulid project
wingetopt - getopt library for Windows compilers
itoa - Fast function for printing integer primitives to a decimal string
abseil-cpp - Abseil Common Libraries (C++)