advent-of-code-ocr VS jmurmel

In past years, I’ve created Advent of Code OCR for Python to convert ASCII letter art from these problems into plain text you can copy and paste.

Python: advent-of-code-ocr module by /u/bsoyka (original post)

The OCR is based on the number of active pixels for each column. The letter "E" has 6 lit pixels in the first column, 3 pixels in the 2nd and 3rd column and 2 pixels in the last column. By looking at the character list (thanks bsoyka on github!) I could craft a lookup table. The four integers will be shifted and added together to get a single integer. The 6,3,3,2 is transformed to 6<<0 + 3<<2 + 3<<4 + 2<<6 = 194 (the bits overlap, I know, but there are no collisions). The index of 194 in this magic list is 4. By adding 65 (ascii value of 'A') I can get the actual character with chr().

See also format.lisp for what I have so far. This will also run with sbcl and/ or abcl. If you've made it this far I'd also appreciate feedback on whether my chosen subset (see the comment at the top of the file) of Common-Lisp's format is somewhat useful and/ or which features you would miss the most.

JMurmel also has commandline flags to turn off language features for experimentation purposes, see e.g. implementing cons, car and cdr in Lambda Calculus.

To my defense, I have started my Lisp compiler/ interpreter mostly for recreational purposes to do the exact opposite of what the checkstyle nazis at my $job demand.

Murmel:

I may be a little late to the party but here's my Murmel solution:

Code is on Github, the latest release with a precompiled jar is at Release V 1.3.

Re: automated tests; there are JUnit tests in https://github.com/mayerrobert/jmurmel/tree/master/lambda/src/test/java, and the files in https://github.com/mayerrobert/jmurmel/tree/master/lambda/src/test/lisp are run automatically, too, and their output and result is checked. Maybe I should add a file HACKING.md or something that gives an intro of the project structure and build system?