Minor adjustments to 2018/hou
Formatting fixes in README.md. Add entry to bugs.md as it will abort due to assertion failure. But this is expected and the entry works fine (open the html file and you'll see that). So INABIAF.
This commit is contained in:
1 parent
cdbf616f1e
commit
90e852c7a7
2 files changed
+27
-4
No files matched your search
+14
-4
@@ -1,6 +1,6 @@
|
||||
# Most likely to top the charts
|
||||
|
||||
Qiming HOU
|
||||
Qiming Hou
|
||||
|
||||
## To build:
|
||||
|
||||
@@ -40,11 +40,21 @@ Try figuring out how to increase the number of different colors, if you can.
|
||||
|
||||
## Author's comments:
|
||||
|
||||
Nowadays almost every programmer needs to do some Web chore. With all the open source stuff readily available, often we just need to call a bunch of libraries to generate an HTML page from a JSON feed.
|
||||
Nowadays almost every programmer needs to do some Web chore. With all the open
|
||||
source stuff readily available, often we just need to call a bunch of libraries
|
||||
to generate an HTML page from a JSON feed.
|
||||
|
||||
This entry takes such decadence to an extreme. It just calls a bunch of libraries to generate an HTML page from a JSON feed, literally. There is no variable (function parameters included), no operator, no flow control statements except a few decorative returns. In compliance to production coding standards, the code is littered with fashionable jargon, doxygen comment, and license text.
|
||||
This entry takes such decadence to an extreme. It just calls a bunch of
|
||||
libraries to generate an HTML page from a JSON feed, literally. There is no
|
||||
variable (function parameters included), no operator, no flow control statements
|
||||
except a few decorative returns. In compliance to production coding standards,
|
||||
the code is littered with fashionable jargon, doxygen comment, and license text.
|
||||
|
||||
As one would expect from such an approach, this program is much more resource intensive than it should be. And one needs a C99-compatible libc (with the common UNIX stuff) to build this and an HTML5-compatible browser to open the result. And it terminates with an assertion failure, but who cares if the web page is already generated?
|
||||
As one would expect from such an approach, this program is much more resource
|
||||
intensive than it should be. And one needs a C99-compatible libc (with the
|
||||
common UNIX stuff) to build this and an HTML5-compatible browser to open the
|
||||
result. And it terminates with an assertion failure, but who cares if the web
|
||||
page is already generated?
|
||||
|
||||
## Copyright and CC BY-SA 4.0 License:
|
||||
|
||||
|
||||
@@ -825,6 +825,19 @@ for now.
|
||||
|
||||
# 2018
|
||||
|
||||
## [2018/hou](2018/hou/prog.c) ([README.md](2018/hou/README.md))
|
||||
## STATUS: INABIAF - please **DO NOT** fix
|
||||
|
||||
When you run it you will see something like:
|
||||
|
||||
```sh
|
||||
$ ./prog < ioccc.json > ioccc.html
|
||||
Assertion failed: (rulez), function C, file prog.c, line 124.
|
||||
Abort trap: 6
|
||||
```
|
||||
|
||||
but this is expected and the file `ioccc.html` will be generated properly.
|
||||
|
||||
|
||||
# 2019
|
||||
|
||||
|
||||
Reference in new issue
Block a user