stores each RESOLVE Conceptual Element as we visit them
function assignment rule
corrected and completed function assignment rule
don't need parameter ensures as givens
no need to modify the ensures clause when we encounter an evaluates mode parameter
changed the output string from ? to '
getting rid of the section id counter in the vcgenerator.
don't really need to keep track of what we visit in a stack (could use the stack visitor if we wanted to keep track...)
renamed a variable
reformatted files
added a stack for assertive codes that we haven't processed yet
skeleton for the if/else rule
complete if/else rule
proof rules are now applied to procedure decs as well
fixed one of the output methods
done with generic variable declarations
fixed an error in modifying the ensures clause with a generic type
now the debug buffer prints the negation of if's in the correct place
reformat the ? doesn't work at the moment
while statement rule