Fix 2001/ollinger bug status in bugs.md

There was some inconsistency as far as whether or not the problem was a
bug or feature, where not enough args would result in a crash. At one
point it seems it was changed to a bug, not a feature, and it is then
that I must have fixed it. However the bugs.md file incorrectly labelled
another entry as ollinger and the README.md for ollinger referred to
something that did not exist or rather it existed but it was for another
entry.

A minor fix in bugs.md has been done as well: change the status name of
using fgets() to not refer to getline(3); rather the description does
that. This is because no other place has that function in the status
line. Doing this is how I found the problem this commit fixes as another
entry should have that status.
This commit is contained in:
Cody Boone Ferguson committed 2023-11-16 11:53:54 -08:00
1 parent b09456bac1
commit d0b2db5220
2 files changed
+5 -24

No files matched your search

-20
View File
@@ -5,32 +5,12 @@ make
```
### Bugs and (Mis)features:
The current status of this entry is:
```
STATUS: INABIAF - please **DO NOT** fix
```
For more detailed information see [2001 ollinger in bugs.md](/bugs.md#2001-ollinger).
## To use:
```sh
./ollinger integer
```
This program will very likely crash or do something else without an arg.
This is supposed to happen. As is written in the
[The Jargon File](http://catb.org/jargon/html/F/feature.html):
```
That's not a bug, that's a feature.
```
### Try:
+5 -4
View File
@@ -302,7 +302,7 @@ NOTE: this does NOT apply to entries under the INABIAF status (though they're
not mutually exclusive in some cases).
## STATUS: uses gets() - change to fgets() if possible (in some cases getline() works)
## STATUS: uses gets() - change to fgets() if possible
NOTE: we're still locating entries and working on fixes with this status so we're not yet
ready for help. We will remove this when we are.
@@ -348,6 +348,9 @@ _NOTE_: this status is _NOT necessarily mutually exclusive_ with the _INABIAF_
during compiling, linking and/or runtime, sometimes causing confusing output (as
noted above).
Sometimes `getline(3)` will work but note that this function also stores the
newline just like `fgets(3)`.
## STATUS: missing file(s) - please provide them
@@ -1426,8 +1429,6 @@ to /dev/null (`2>/dev/null`).
## 1996 jonth
### STATUS: INABIAF - please **DO NOT** fix
### STATUS: INABIAF - please **DO NOT** fix
### Source code: [1996/jonth/jonth.c](1996/jonth/jonth.c)
### Information: [1996/jonth/README.md](1996/jonth/README.md)
@@ -1926,7 +1927,7 @@ Although it is independent of endianness both systems need the same character
set. In other words both have to be ASCII or EBCDIC - not one of each.
## 2001 ollinger
## 2001 schweikh
### STATUS: INABIAF - please **DO NOT** fix