Files
ioccc/1984/decot/README.md
T
Cody Boone Ferguson cb8d8924a7 Improve links to bugs.html in README.md files
In other words rather than have the link name in the form of:

    1984 decot bugs

it is now:

    1984/decot in bugs.html

so that it matches how the entry itself looks (as in how it's
identified) and to say where (what file) it is (in). The reason it says
'in bugs.html' rather than 'bugs' (saying that the entry has bugs) is
because not all are bugs and it's saying where to see it anyway. But
some are features, others are missing links or files or other things
like that and to keep the same form it now says 'in bugs.html'.

This was done with my sgit(1) tool like:

    sgit -e 's,\([0-9][0-9][0-9][0-9]\) \([-a-z\.0-9]*\) bugs,\1/\2 in bugs.html,g' '*/*md'

The link to bugs.html itself has the path '../../bugs.html'. This is
important as it's meant to be rendered in the browser. At first this was
not remembered and I did something like:

    sgit -e 's,\[\([0-9][0-9][0-9][0-9]\) \([-a-z\.0-9]*\) bugs\](../../bugs.html,\[\1/\2 in bugs.html\](%%REPO_URL%%/bugs.html,g' '*/*md'

but this was changed to the simpler one due to the problem described
above. It's worth putting this note here as a reminder, though, so I
have included it here.
2024-05-04 09:21:09 -07:00

1.9 KiB

To build:

    make all

NOTE: there is an alternate version which will only work if you have an old enough compiler or a compiler that supports -traditional-cpp. The original code was fixed in 2023 to not require this.

Bugs and (Mis)features:

The current status of this entry is:

    STATUS: INABIAF - please **DO NOT** fix

For more detailed information see 1984/decot in bugs.html.

To use:

    ./decot

Alternate code:

This alternate code, the original, requires a compiler that supports -traditional-cpp or an old enough compiler. If you have such a compiler you can use this version.

Alternate build:

    make alt

Alternate use:

    ./decot.alt

Judges' remarks:

This program prints out what looks like a fragment of C code.

Is this a bug or is this a feature? To help choose the judges offer this one comment: understand remarks!

Historical remarks:

Some new (in 1984) compilers disliked line 15 of the original source, so we changed it from:

    for(signal=0;*k * x * __FILE__ *i;) do {

to:

    for(signal=0;*k *x * __FILE__ *i;) do {

To see what we mean look at the original source file. The alternate code is the version that has this modification. The fixed version has instead:

    for(signal=0;*k *= * __FILE__ *i;) do {

Author's remarks:

No remarks were provided by the author.