fcl does not understand files that have lines terminated by cr-nl
Earlier today I was emailed a .fcl file which I saved to disk and then could not use. The problem turned out to be that the file had lines terminated DOS style with cr-nl, not with a simple nl.
I have attached a one line file, foo.fcl, that contains an example:
Hopefully the error is not removed by redmine. Anyway, when I ran this through art it gave the error:
Failed to parse the configuration file 'foo.fcl' with exception
---- Malformed #include directive: BEGIN
at line 1 of file ./foo.fcl
---- Malformed #include directive: END
Art has completed and will exit with status 7002.
Note that it gives this same message whether or not the included file actually exists in FHICL_FILE_PATH.
I request that FHICL be updated to be able to handle files with lines terminated by cr-nl.
#1 Updated by Kyle Knoepfel over 5 years ago
- Category set to Infrastructure
- Status changed from New to Accepted
- Assignee set to Christopher Green
- Target version set to 1.13.00
- Estimated time set to 2.00 h
- SSI Package fhicl-cpp added
- SSI Package deleted (
Time estimate depends on our initial analysis that this is a trivial change to the white-space skipper being accurate.