Format fixes in 1990/scjones/README.md
This includes moving from the author's comments the note from the judges that he had sent a note to the judges asking something about the award title along with the judges' reply. It seemed like the more appropriate place to have it.
This commit is contained in:
1 parent
ebd000e60c
commit
a9d9250afb
1 file changed
+44
-42
+44
-42
@@ -1,23 +1,26 @@
|
|||||||
# ANSI Committee's Worst Abuse of C
|
# ANSI Committee's Worst Abuse of C
|
||||||
|
|
||||||
Larry Jones
|
Larry Jones
|
||||||
SDRC
|
SDRC
|
||||||
2000 Eastman Dr
|
2000 Eastman Dr
|
||||||
Milford, OH 45150
|
Milford, OH 45150
|
||||||
USA
|
USA
|
||||||
|
|
||||||
## To build:
|
## To build:
|
||||||
|
|
||||||
make all
|
```sh
|
||||||
|
make all
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
Modern compilers failed to compile this entry:
|
Modern compilers failed to compile this entry:
|
||||||
|
|
||||||
scjones.c:1:7: error: expected ';' after top level declarator
|
```c
|
||||||
char*a??(??)=??<
|
scjones.c:1:7: error: expected ';' after top level declarator
|
||||||
^
|
char*a??(??)=??<
|
||||||
;
|
^
|
||||||
|
;
|
||||||
|
```
|
||||||
|
|
||||||
but we were able to get it to compile with modern compilers by specifying the
|
but we were able to get it to compile with modern compilers by specifying the
|
||||||
`-ansi` flag with a tip from [Yusuke Endoh](/winners.html#Yusuke_Endoh). Thank
|
`-ansi` flag with a tip from [Yusuke Endoh](/winners.html#Yusuke_Endoh). Thank
|
||||||
@@ -29,43 +32,42 @@ compiler option `-trigraphs` would also have worked.
|
|||||||
|
|
||||||
## To run:
|
## To run:
|
||||||
|
|
||||||
./scjones
|
```sh
|
||||||
|
./scjones
|
||||||
|
```
|
||||||
|
|
||||||
## Judges' comments:
|
## Judges' comments:
|
||||||
|
|
||||||
The addition of trigraphs has made it easier to make programs
|
The addition of trigraphs has made it easier to make programs hard to read. It
|
||||||
hard to read. It was a dark and stormy night for C when the
|
was a dark and stormy night for C when the ANSI C committee added trigraphs to
|
||||||
ANSI C committee added trigraphs to the standard. Too bad
|
the standard. Too bad that they didn't just simply require a more reasonable
|
||||||
that they didn't just simply require a more reasonable ISO
|
ISO character set.
|
||||||
character set.
|
|
||||||
|
The Author sent us this note after he was informed that he won:
|
||||||
|
|
||||||
|
> Although I am quite grateful for the "ANSI Committee's Worst Abuse of C" title
|
||||||
|
> (were you aware that I am a member of the committee or is the double meaning
|
||||||
|
> unintentional?), I was really hoping for something more along the lines of
|
||||||
|
> "Closest Resemblance to Line Noise." :-)
|
||||||
|
|
||||||
|
... it was unintentional.
|
||||||
|
|
||||||
|
|
||||||
## Author's comments:
|
## Author's comments:
|
||||||
|
|
||||||
Since this year's contest is dedicated to ANSI C, here is a
|
Since this year's contest is dedicated to ANSI C, here is a strictly conforming
|
||||||
strictly conforming entry. In accordance with the ANSI
|
entry. In accordance with the ANSI definition of a strictly conforming program
|
||||||
definition of a strictly conforming program it does not produce
|
it does not produce output dependent on any unspecified, undefined, or
|
||||||
output dependent on any unspecified, undefined, or implementation
|
implementation defined behavior, and it does not exceed any of the minimum
|
||||||
defined behavior, and it does not exceed any of the minimum
|
implementation limits. It adheres to all of the syntactic and semantic
|
||||||
implementation limits. It adheres to all of the syntactic and
|
constraints of the standard: it `#include`s the relevant headers for the
|
||||||
semantic constraints of the standard, #includes the relevant
|
functions it uses, and it uses the `EXIT_SUCCESS` and `EXIT_FAILURE` macros to
|
||||||
headers for the functions it uses, and uses the EXIT_SUCCESS and
|
return a correct success/fail status to the invoking program. It also uses
|
||||||
EXIT_FAILURE macros to return a correct success/fail status to
|
trigraphs for characters which are not in the `Invariant Code Set` of `ISO
|
||||||
the invoking program. It also uses trigraphs for characters
|
646:1983`, so it will be portable to machines with deficient (from C's
|
||||||
which are not in the Invariant Code Set of ISO 646:1983, so it
|
standpoint) character sets. In short, it should be very widely portable. As an
|
||||||
will be portable to machines with deficient (from C's standpoint)
|
extra added attraction, all of the lines are under 72 characters long, which
|
||||||
character sets. In short, it should be very widely portable. As
|
would allow for sequence numbers to be punched in columns 73-80 :-).
|
||||||
an extra added attraction, all of the lines are under 72
|
|
||||||
characters long, which would allow for sequence numbers to be
|
|
||||||
punched in columns 73-80 :-).
|
|
||||||
|
|
||||||
[[ The Author sent us this note after he was informed that he won ]]
|
|
||||||
|
|
||||||
> Although I am quite grateful for the "ANSI Committee's Worst Abuse of C" title
|
|
||||||
(were you aware that I am a member of the committee or is the double meaning
|
|
||||||
unintentional?), I was really hoping for something more along the lines of
|
|
||||||
"Closest Resemblance to Line Noise." :-)
|
|
||||||
|
|
||||||
[[ ... it was unintentional ]]
|
|
||||||
|
|
||||||
## Copyright and CC BY-SA 4.0 License:
|
## Copyright and CC BY-SA 4.0 License:
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user