Fixes in 1998/schweikh1/README.md
There was 'I' in the README.md that was an artefact left over from before the thanks file was introduced so that sentence was removed. The thanks file was slightly updated too wrt this entry both as a new category of fixes (the alternate code I made so that it works with macOS but also referring to the README.md file).
This commit is contained in:
1 parent
7183971943
commit
bc579cd72e
2 files changed
+16
-14
No files matched your search
@@ -52,11 +52,10 @@ respectively, 44 and 46. But how does this work? Well the string is:
|
|||||||
|
|
||||||
The first number means: the length starting from 0 up through the `>`. The
|
The first number means: the length starting from 0 up through the `>`. The
|
||||||
second number is the same starting point but up through the `\0` which is why
|
second number is the same starting point but up through the `\0` which is why
|
||||||
it's +2. Somehow it was basic intuition that made me figure out these two
|
it's +2. But what happens if only the first number is updated? Most of the
|
||||||
numbers and a quick test confirmed it. But what happens if only the first number
|
output will be just `#define` by itself; in the cases where there was text after
|
||||||
is updated? Most of the output will be just `#define` by itself; in the cases
|
that it was macros that certainly were not defined. There might have been other
|
||||||
where there was text after that it was macros that certainly were not defined.
|
errors as well.
|
||||||
There might have been other errors as well.
|
|
||||||
|
|
||||||
This allows for opening the right files. The problem with the macOS is
|
This allows for opening the right files. The problem with the macOS is
|
||||||
`/usr/include` does not exist: instead it's
|
`/usr/include` does not exist: instead it's
|
||||||
|
|||||||
+12
-9
@@ -13,13 +13,15 @@ Ferguson](/winners.html#Cody_Boone_Ferguson) who is responsible for many of the
|
|||||||
improvements including many, many **very complicated bug fixes** such as
|
improvements including many, many **very complicated bug fixes** such as
|
||||||
[2001/anonymous](2001/anonymous/anonymous.c) and
|
[2001/anonymous](2001/anonymous/anonymous.c) and
|
||||||
[2004/burley](2004/burley/burley.c), making entries not require
|
[2004/burley](2004/burley/burley.c), making entries not require
|
||||||
`-traditional-cpp` (which are **very complicated fixes**), fixing entries to compile
|
`-traditional-cpp` (which are **very complicated fixes**), fixing entries to
|
||||||
with clang, providing alternate code where useful or necessary, fixing where
|
compile with clang, fixing entries to work with macOS (some of which are **very
|
||||||
possible dead links and otherwise removing them, typo and consistency fixes and
|
complicated** such as [1998/schweikh1](1998/schweikh1/schweikh1.c)), providing
|
||||||
writing the [sgit tool](https://github.com/xexyl/sgit) that we've published on the
|
alternate code where useful or necessary, fixing where possible dead links and
|
||||||
website. Thank you **very much** for your extensive efforts in helping improve
|
otherwise removing them, typo and consistency fixes and writing the [sgit
|
||||||
the IOCCC presentation of past IOCCC winners and making many many past entries
|
tool](https://github.com/xexyl/sgit) that we've published on the website. Thank
|
||||||
work with modern systems!
|
you **very much** for your extensive efforts in helping improve the IOCCC
|
||||||
|
presentation of past IOCCC winners and making many many past entries work with
|
||||||
|
modern systems!
|
||||||
|
|
||||||
[Yusuke Endoh](/winners.html#Yusuke_Endoh) supplied a number of
|
[Yusuke Endoh](/winners.html#Yusuke_Endoh) supplied a number of
|
||||||
important bug fixes to a number of past IOCCC winners. Some of
|
important bug fixes to a number of past IOCCC winners. Some of
|
||||||
@@ -838,8 +840,9 @@ enough though this did not seem to be an issue though I cannot explain why. He
|
|||||||
notes that it works fine with `clang` as well as `gcc` (which is what is used
|
notes that it works fine with `clang` as well as `gcc` (which is what is used
|
||||||
but in macOS - see below for alternate code - `gcc` is clang).
|
but in macOS - see below for alternate code - `gcc` is clang).
|
||||||
|
|
||||||
Additionally Cody provided an alternate version for macOS. See the README.md
|
Additionally Cody provided an alternate version for macOS. The fix is
|
||||||
file for details on the alternate version.
|
rather complicated but very interesting. See the README.md file for details on
|
||||||
|
how it works and how to use it.
|
||||||
|
|
||||||
|
|
||||||
## [1998/schweikh2](1998/schweikh2/schweikh2.c) ([README.md](1998/schweikh2/README.md]))
|
## [1998/schweikh2](1998/schweikh2/schweikh2.c) ([README.md](1998/schweikh2/README.md]))
|
||||||
|
|||||||
Reference in new issue
Block a user