v0.7.1

• Makefile: automatic source dependency tracking for rebuilds
• Bug fix: do not 'process special chars' in file reads, only when
  adding instructions
• Replaced old test suite with new, more robust one written in Bash++

v0.7.0

• The dream of instruction optimization has finally arrived!
  The -O option allows you to specify the optimization level for
  your instructions in polonius-editor. -O0 disables optimizations,
  -O1 applies theorems 0 and 1 as outlined in the wiki page
  detailing the mathematics, and -O2 applies theorems 0, 1, 3 and 4.
  -O2 is the default unless otherwise specified.
  At the moment, the instruction sequence is optimized before
  execution, however, the File insert and remove functions have not
  been modified to execute multiple operations in a single pass
  of the file yet. This will be done very soon.
  See https://github.com/rail5/polonius/wiki/Instruction-Optimization
  for more information on how this is done.

v0.6.1

• Do not reset search mode on -f
  Previously, -f set search mode to 'normal'
  This would mean that if a search command was entered with -e
  preceding -f, the search mode would be reset to normal from regex
  mode. This would be incorrect behavior

v0.6.0

• Merge pull request #37 from rail5/total-rewrite
  The editor and reader have been completely re-written
  from scratch.
  This closes #23 and #16
• Use all CPU cores for builds unless otherwise specified
• Support for the 'end' keyword has been removed

v0.5.16

• Super hacky fix for a bug inserting to files of 0 size
  A TOTAL rewrite of both the editor and the reader is coming
  very, very, very, very soon

v0.5.15

• Improved help messages Much better formatting
• Patched a bug in compilation on Ubuntu

v0.5.14

• Added -f option to polonius-editor
  The -f option allows the user to specify a FILE which contains our
  instruction sequences, rather than specifying those instructions
  via the command line.
  E.g.: polonius-editor ./text.txt -f ./instructions.txt
• Patched another bug found by the test suite in which Polonius
  couldn't handle blank lines in instruction sequences

v0.5.13

• Polonius can now accept single-line 'delimited' instructions
  Multiple instructions of the same type can now be given on a single
  line in the format: INSERT 0 abc; 10 def; 20 ghi
  Or: REPLACE 0 abc; 10 def; 20 ghi
  Or: REMOVE 0 2; 10 12; 20 22
  Literal semicolons can also be inserted by escaping the semicolon
  with a backslash, as in:
  INSERT 10 along the wall to keep\; and slept
• 'Instruction sets' have been renamed to the more appropriate
  'Instruction sequences'
  This gives a clearer idea of what they are
• Added loads more tests
• Patched another small bug found by the tests

v0.5.12

• Added infrastructure to run automated tests on changes to Polonius
  These will help to make sure that functionality isn't broken by any
  code changes.
• Patched a small bug in INSERT which was found by this new automated
  testing infrastructure

v0.5.11

• Use the program_name variable instead of hard-coding the name into
  error messages
• Make sure that the user provides instructions to execute
• Refuse to create a new file if the instruction sequence is invalid.
  If we're creating a new file, the first instruction should be an
  INSERT
• Immediately write a newline char when creating a new file