Added 'fatal' option to addCondition; enhancements to runTests, and added unit test for runTests

git-svn-id: svn://svn.code.sf.net/p/pyparsing/code/trunk@348 9bf210a0-9d2d-494c-87cf-cfb32e7dff7b

1 files changed, 7 insertions, 3 deletions

diff --git a/src/CHANGES b/src/CHANGES
index 1a50a73..d2aa8ad 100644
--- a/src/CHANGES
+++ b/src/CHANGES
@@ -5,15 +5,16 @@ Change Log
 Version 2.1.4 - 

 ------------------------------

 - Split out the '==' behavior in ParserElement, now implemented

-  as the matches() method. Using '==' for string test purposes will

-  be removed in a future release.

+  as the ParserElement.matches() method. Using '==' for string test 

+  purposes will be removed in a future release.

 

 - Expanded capabilities of runTests(). Will now accept embedded

   comments (default is Python style, leading '#' character, but 

   customizable). Comments will be emitted along with the tests and

   test output. Useful during test development, to create a test string

   consisting only of test case description comments separated by 

-  blank lines, and then fill in the test cases.

+  blank lines, and then fill in the test cases. Will also highlight

+  ParseFatalExceptions with "(FATAL)".

 

 - Added a 'pyparsing_common' class containing common/helpful little 

   expressions such as integer, float, identifier, etc. I used this 

@@ -23,6 +24,9 @@ Version 2.1.4 -
 - Minor enhancement to traceParseAction decorator, to retain the 

   parse action's name for the trace output.

 

+- Added optional 'fatal' keyword arg to addCondition, to indicate that

+  a condition failure should halt parsing immediately.

+

 

 Version 2.1.3 - May, 2016

 ------------------------------