Files
Cody Boone Ferguson 22e483723c Make bug statuses in index.html files quotes
Instead of code blocks the bug / (mis)features statuses are quoted
rather than in a code block. In the case that there is more than one a
line break was added at the end of all but the last one.

A bug status was renamed to be slightly more correct (maybe more than
one was renamed for the same purpose but at least one was).

The bug statuses in the quotes are now bold to let them stand out
better.
2024-07-17 09:54:33 -07:00

130 lines
3.1 KiB
Markdown

## To build:
``` <!---sh-->
make
```
### Bugs and (Mis)features:
The current status of this entry is:
> **STATUS: INABIAF - please DO NOT fix**
For more detailed information see [2019/burton in bugs.html](../../bugs.html#2019_burton).
## To use:
``` <!---sh-->
./prog < file
./cow file
```
## Try:
``` <!---sh-->
./try.sh
```
## Judges' remarks:
A tiny, but punctually correct way of POSIX counting for text files. This one
line, one word, 127 character beauty continues to expand the number of classic
unix utilities available as winning entries.
You might find the author's [commentary on one liners](on.one.liners.txt)
interesting.
## Author's remarks:
### Synopsis:
Feed it anything on `stdin`.
The output should look familiar.
Compiles cleanly with:
``` <!---sh-->
WARN="-Wno-implicit-int -Wno-missing-variable-declarations -Wno-parentheses"
cc -Wall -Wextra -Weverything -pedantic $WARN -include stdio.h -o prog prog.c
```
### Description:
Included is a test script, useful for the corner cases. As in all good Unix
programs, it is silent upon success; any output demonstrates an error.
### NOTICE to those who wish for a greater challenge:
**If you want a greater challenge, don't read any further**:
just try to understand the program without running the command below.
If you get stuck, come back and run the following command:
``` <!---sh-->
out=cat ./check.sh ./prog
```
Instead of checking correctness, the
[check.sh](%%REPO_URL%%/2019/burton/check.sh) script can simply
output the results:
Interestingly, and a spoiler here: macOS and FreeBSD implement the common
utility "correctly". CentOS and Ubuntu both share a "flawed" utility that
changes output format based upon input redirection or pipeline(!). As well, the
latter two also behave slightly differently on what they count as whitespace:
`\a` and `\b` are both counted whitespace(!), even though the relevant man pages
on these systems omit these characters from the description.
This program follows FreeBSD and macOS, the arbiters of correct for these purposes.
### Limits:
Requires the C locale and ASCII character set.
Input should be less than ten million octets "toavoidthisproblem".
### See Also:
You can enjoy this code from beginning to end.
No whitespace was harmed in the creation of this program.
All your base belong to us, but the constants seem a bit ... off?
### Bonus
The script [cow.sh](%%REPO_URL%%/2019/burton/cow.sh) provides a closer analog, and perhaps a more useful
interface.
Included is a version without compilation warnings:
``` <!---sh-->
cc -Wall -Wextra -Weverything -pedantic -include stdio.h -o prog.clean prog.clean.c
```
### Bugs
The flags are not supported. Although they could easily be added into `cow.sh`.
This exercise left to the reader.
<!--
Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/
-->