further assumption: fixedStartValues and fixedEndValues values
adhere to target type, as well as target units.

in present parsers, fixedStartValues and fixedEndValues is only used for
strings, so this change should be backwards-compatible

Fix stream

Fix stream handling:
1) calling conventions for parseFile in stream mode
2)  add 'outFile' option to mainFunction stream protocol
3) sort json dict keys and start/endRe events
4) add catchall for exceptions in streaming mode
5) remove unnecessary 'try' block in parseStep, exceptions are treated by (4) or cause clean parser suicide in non-stream mode

See merge request !4

either exception is treated within mainFunction/stream, or it will kill the
parser, as it should

Somehow there was a mixup (probably caused by my merge), and the wrong function was called inside the addRealValue() of CachingBackend. Now things should be ok.

Some renamings in CacheService, better warnings when trying to use the wrong backend function for arrays.

Hooks with matches



See merge request !3

Explicit string conversion

nice :)

See merge request !2

this way, adHoc(parser) hooks can access the information extracted by
startReStr via parser.lastMatch

startReStr=r"(?P<something>\d+)" as parser.lastMatch['something']

create dictionary with all matched groups/values and return it.

- metaName (without unit suffix)
- final, numeric-type and possibly unit-converted value

transformers assign custom strValueTransform functions to named groups
in SimpleMatcher regular expressions.
Implemented analogously to the existing 'converters' mechanism
for unit conversion.

Name of transformation method starts with 'strValueTransform_'
and then have a 'pseudo-unit-name' starting with 'str', which can then be
referenced as a 'unit' in regex group names.
Output units of transform method can be specified as function attribute
'units'
    def strValueTransform_strDate(self.string)
        ....
    strValueTransform_strDate.units = 's'
would than be used, if you have
    (?P<time_run_date_start__strDate>...)
in your regex.

fix issue where json would be printed to stdout even though outF is another file

While we are at it, removed unnecessary global declarations and add what I presume were missing return statements

Since I am unsure how to properly test these things I submit it for review.

See merge request !1

fix issue where json would be printed to stdout even though outF is another file.  While we are at it, removed unnecessary global declarations and add what I presume were missing return statements

superContext.coverageIgnore is a python RE object, and if it matches,
line color is turned to blue

if a section is not forwarded none of the children are