cet-is » fhicl » fhicl-cpp

Attempting to write a regex into a FHiCL parameter, I found that the FHiCL parser "silently" replaces the value which failed parsing with "oops".
For example, a FHiCL file with content:

pattern: "$\d+^"

is seen by fhicl-expand like:

Policy is 1; path is "FHICL_FILE_PATH" 
pattern: "$\d+^" 

but fhicl-dump shows it as

# Produced from 'fhicl-dump' using:
#   Input  : pattern.fcl
#   Policy : cet::filepath_maker
#   Path   : "FHICL_FILE_PATH" 

pattern: oops

I would rather see the parser throw an exception in these cases.

(I am sure there is a way to correctly escape these strings... I ended up being more standard and using [[:digit:]] instead of \d, which is just as good.)