Relevant: https://github.com/SixArm/usv
They seem to believe they have monopolized Unicode Separated Values:
The USV project aims to become a free open source IANA standard, much like the…
It's less in accord with IEEE 754 and more that we are applying IEEE 754 (or, more specifically, Rust is - and even then, it's the processor itself I think that is doing the floating point operations). I would say "Due to IEEE 754 (the IEEE Standard for Floating Point Arithmetic) limitations, rounding errors may occur. And not "in line" with the standard but simply "that can be represented".
I don't like the use of the Unicode apostrophe here because it could mess with literal text lookups. Nobody likes a No occurrences of "doesn't" because of fancy rune voodoo.
"either from given arguments, or, in their absence, standard input" - right now you have "parse" twice in there which feels weird.
I believe the past tense of "output" is "output" - also, I'm having a hard time understanding what you're trying to convey here - shouldn't rpn print the last number on the stack? It sounds like it prints the last result of any algebraic operations but ignores further given numbers.
qi(1): The qi shell
Should piping be done by the shell?
I've had an old program idea that I'm still working on called pspipe(1) - it pipes given commands. So pspipe [ cat ] [ less ] is equivalent to `sh -c 'cat…
rpn(1) - reverse polish notation
We discussed bitwise operators not being useful for this calculator as it's floating point. I'm working on another RPN implementation (srpn(1) - simpler rpn) that might be nice for an Extras…
rpn(1) - reverse polish notation
Comparisons might be tricky because it's hard to compare floating point numbers. 0.3 doesn't always equal 0.3 bit-by-bit. Maybe it would be better to have a ~= for equality ± some value and…
scroll(1) – pager
I have a particularly bad one in my source tree. It was less useful once I'd figured out I could scroll my xterms but nowadays I just use…
rtfm(1) - manual pages
Could # headers be specifically for title/section metadata?
For example, roff:
.TH PAGE 1
and my proposed equivalent usage in doc:
# PAGE(1)
Or PAGE 1 or…