Diagramming a bit more

I got a bit too eager with my tokenizer. I started building the lexer into it... and it got bad.

So. What's going on?

  1. Too little code segmentation. It's all jumbled together instead of modular.
  2. Program dies when given unexpected input (it should fail gracefully).
  3. I get confused when I open the file.

These are all pretty bad outcomes, considering Carp is a small and young project, developed exclusively by me.

Here's how I plan to remedy this:

  1. More flowcharts and other related diagrams for sure.
  2. Add logic that allows the program to process bad input (so it can alert the programmer what's wrong).
  3. Add documentation wherever possible.

Aside from Carp, I have some other exciting news about photos and photography and whatnot. I found this old film camera (a Nikon N6006) from ages ago — and the film was still in it! I am getting it developed tomorrow.

My friend Shy is really into film photograhy, and her work is gorgeous. I may delve into film photography. After all, I do have an unused roll of black and white film sitting on my shelf...