optparse
ucd-generate
Our great sponsors
optparse | ucd-generate | |
---|---|---|
5 | 3 | |
314 | 90 | |
- | - | |
0.0 | 6.6 | |
6 months ago | 3 months 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.
ucd-generate
-
Using unwrap() in Rust is Okay
So you're saying that the 'expect()' message when a regex compilation error occurs should be a translation from a terse domain specific language to bloviating prose? :-)
What 'expect()' message would you write for this regex? https://github.com/BurntSushi/ucd-generate/blob/6d3aae3b8005...
I think 'unwrap()' there is perfectly appropriate.
> I think it'd be desirable to have a `.unwrap_with_context("Context: {}")`, and the you'd get `Context: Inner Panic Info`.
Why?
-
Debian discusses vendoring again
I've also embedded Unicode tables a number of times. It's very easy to do, and I do it enough that I even have a tool to do it. Having tooling and scripts to do it is important for reasons of provenance and also for when the tables need to be updated (every year or so).
-
Announcing chr 1.0.0: A command-line tool that gives information about Unicode characters
ucd-generate for generating Unicode tables. It is what the regex crate uses to generate all of its tables, and it supports many properties already. It also provides a way to represent Unicode character names in a compressed data structure.
What are some alternatives?
getopt - POSIX getopt() as a portable header library
ripgrep-all - rga: ripgrep, but also search in PDFs, E-Books, Office documents, zip, tar.gz, etc.
perl5 - 🐪 The Perl programming language
itoa - Fast function for printing integer primitives to a decimal string
rust-fnv - Fowler–Noll–Vo hash function
itoa - Fast integer to ascii / integer to string conversion
unicode-xid
wingetopt - getopt library for Windows compilers
character - tool for character manipulations