pegs module: bugfixes for the anchor ^; pegs.replace now does what the docs say

todo.txt

@@ -5,8 +5,11 @@ High priority (version 0.8.12)
 * add --deadlock_prevention:on|off switch? timeout for locks?
 * built-in serialization
 - bug: invoking a generic iterator twice triggers a code gen bug (titer2)
-- pegs: the anchor '^' does not work because many procs use a linear search
-  and matchLen()
+- bug: forward proc for generic seems broken
+- sorting with leads to a strange memory corruption!
+  --> system.swap or genericAssign is broken! And indeed, if reference counts
+      are not modified and the GC is triggered in between a swap, bad things
+      may happen!
 
 
 version 0.9.0
@@ -30,11 +33,6 @@ Bugs
 - bug: generic assign still buggy
   - Optimization: If we use a temporary for the result anyway the code gen
     should make use of this fact to generate better code...
-- bug: forward proc for generic seems broken
-- sorting with leads to a strange memory corruption!
-  --> system.swap or genericAssign is broken! And indeed, if reference counts
-      are not modified and the GC is triggered in between a swap, bad things
-      may happen!
 
 
 version 0.9.XX
@@ -111,7 +109,10 @@ Version 2
     
 - the two other parsers
 - rethink the syntax: distinction between expr and stmt is unfortunate; 
-  indentation handling is quite complex too
+  indentation handling is quite complex too; problem with exception handling
+  is that often the scope of ``try`` is wrong and apart from that ``try`` is
+  a full blown statement; a ``try`` expression might be a good idea to make
+  error handling more light-weight
 
 
 Low priority