Updated documentation.

README

@@ -141,7 +141,7 @@ Otherwise, the dump is printed to stdout.
 -- 
 
 sieve-test [-r <recipient address>][-s <envelope sender>]
-           [-m <mailbox>][-d <dump filename>][-c] <scriptfile> <mailfile>
+           [-m <mailbox>][-d <dump filename>][-c][-t] <scriptfile> <mailfile>
 
 Reads mail message from the specified mailfile and executes the specified sieve 
 script to produce a verdict. This prints an execution dump with the instructions 
@@ -155,6 +155,8 @@ Options:
   -d  causes a dump of the generated code to be written to the specified
       file. Using - as filename causes the dump to be written to stdout
   -c  force compilation (ignore any existing binary)
+  -t  enable trace debugging; prints all encountered byte code instructions on
+      stdout. 
 
 --
 

TODO

@@ -21,6 +21,8 @@ Next (in order of descending priority/precedence):
 	- Implement limits recommended by the variables RFC (5229)
 	- Malicious/Broken binary can allocate large variable storage
 * Finish the test suite for the base functionality
+* Improve byte code dumping and trace functionality to be a little more 
+  user-friendly
 * Make sure cmusieve can be replaced seamlessly with the new plugin.
 
 * ## MAKE A FIRST RELEASE (0.1.x) ##