mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixes in 2019/burton/Makefile and README.md

Browse Source 
The Makefile had a bad character, a '%' instead of a '$' which caused a
rule to fail.

Format fixes in README.md.

There is one thing I'm not sure about. It appears to be a mistake but
I'm not sure if there is some meaning. Line 66:

    Input should be less than ten million octets toavoidthisproblem.

But the last 'word' should be, at least if it is a mistake, four words.
I have not changed it as the context was not clear enough to be sure it
was incorrect. This can be dealt with another time.
This commit is contained in:
Cody Boone Ferguson committed 2023-04-02 12:06:57 -07:00
1 parent e0a9b41a32
commit 11bb20257f
2 files changed
+17 -16
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2019/burton/Makefile
+1 -1
View File
@@ -135,7 +135,7 @@ ${PROG}.clean: ${PROG}.clean.c
${CC} ${CFLAGS} $< -o $@ ${LIBS} ${CC} ${CFLAGS} $< -o $@ ${LIBS}
remarks: README.md remarks: README.md
%{RM} -f $@ ${RM} -f $@
${CP} $? $@ ${CP} $? $@
correct: newlines remarks 256 check correct: newlines remarks 256 check
2019/burton/README.md
+16 -15
View File
@@ -1,6 +1,6 @@
# Best one-liner # Best one-liner
Dave Burton Dave Burton
## To build: ## To build:
@@ -28,7 +28,7 @@ unix utilities available as winning entries.
## Author's comments: ## Author's comments:
### Synopsis ### Synopsis:
Feed it anything on stdin. Feed it anything on stdin.
The output should look familiar. The output should look familiar.
@@ -40,31 +40,32 @@ WARN="-Wno-implicit-int -Wno-missing-variable-declarations -Wno-parentheses"
cc -Wall -Wextra -Weverything -pedantic $WARN -include stdio.h -o prog prog.c cc -Wall -Wextra -Weverything -pedantic $WARN -include stdio.h -o prog prog.c
``` ```
### Description ### Description:
Included is a test script, useful for the corner cases. Included is a test script, useful for the corner cases. As in all good Unix
As in all good Unix programs, it is silent upon success; any output demonstrates an error. programs, it is silent upon success; any output demonstrates an error. Instead
Instead of checking correctness, the check script can simply output the results: of checking correctness, the check script can simply output the results: (The
(The Makefile contains the spoiler): Makefile contains the spoiler):
```sh ```sh
out=cat ./check ./prog out=cat ./check ./prog
``` ```
Interestingly, and a spoiler here: MacOS and FreeBSD implement the common utility "correctly". Interestingly, and a spoiler here: macOS and FreeBSD implement the common
CentOS and Ubuntu both share a "flawed" utility that changes output format based upon input redirection or pipeline(!). utility "correctly". CentOS and Ubuntu both share a "flawed" utility that
As well, the latter two also behave slightly differently on what they count as whitespace: changes output format based upon input redirection or pipeline(!). As well, the
\a and \b are both counted whitespace(!), even though the relevant man pages on these systems latter two also behave slightly differently on what they count as whitespace:
omit these characters from the description. `\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. This program follows FreeBSD and macOS, the arbiters of correct for these purposes.
### Limits ### Limits:
Requires the C locale and ASCII character set. Requires the C locale and ASCII character set.
Input should be less than ten million octets toavoidthisproblem. Input should be less than ten million octets toavoidthisproblem.
### See Also ### See Also:
You can enjoy this code from beginning to end. You can enjoy this code from beginning to end.
No whitespace was harmed in the creation of this program. No whitespace was harmed in the creation of this program.