Project

General

Profile

Bug #23656

Parsing of value silently fails: oops

Added by Gianluca Petrillo about 2 months ago. Updated about 2 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
11/26/2019
Due date:
% Done:

0%

Estimated time:
Duration:

Description

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.)

History

#1 Updated by Kyle Knoepfel about 2 months ago

  • Status changed from New to Feedback

Seems to be a bug. Have you tried this with an actual art job, and you still get the "oops" problem?

#2 Updated by Gianluca Petrillo about 2 months ago

Yes. That was, in fact, the context in which I encountered the issue.



Also available in: Atom PDF