Author:

• Name: Yusuke Endoh
  Location: JP - Japan

To build:

    make

To use:

    ./prog

Try:

    ./try.sh

What happens if you do

    ./prog prog.c

?

Judges’ remarks:

Clever use of the C99 complex data type. The obfuscation directory contains clues as to how some winning authors create / edit programs into ASCII shapes.

With the source from the obfuscation directory could you make the code render for a larger terminal window? How about adding more glyphs?

Author’s remarks:

No! Try not. Do, or do not. There is no try.

    cc -std=c99 prog.c
    ./a.out
    ./a.out hello.txt
    ./a.out yoda.txt
    ./a.out bear.txt

Primary files

• prog.c - entry source code
• Makefile - entry Makefile
• prog.orig.c - original source code
• bear.txt - sample input
• hello.txt - sample input
• try.sh - script to try entry
• yoda.txt - sample input
• obfuscation/code.c - main logic to program to obfuscate entry
• obfuscation/gen.rb - ruby code to compose items and prog.c in artistic way
• obfuscation/glyphs.txt - glyphs data for obfuscation/gen.rb
• obfuscation/index.html - obfuscation information web page
• obfuscation/prog.c - obfuscated source code
• obfuscation/tmpl.txt - template for obfuscation/gen.rb output

Secondary files

• 2020_endoh2.tar.bz2 - download entry tarball
• README.md - markdown source for this web page
• .entry.json - entry summary and manifest in JSON
• .gitignore - list of files that should not be committed under git
• obfuscation/index.md - markdown source for deobfuscationr/index.html
• .path - directory path from top level directory
• index.html - this web page

Jump to: top