Project

General

Profile

Bug #1847

Is this a bug (diplicate key precedence reversed in nested context)?

Added by Rob Kutschke over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Infrastructure
Target version:
Start date:
09/14/2011
Due date:
% Done:

100%

Estimated time:
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

Consider the following FHICL fragment

process_name : fhiclTest00

physics : {

analyzers: {
hi : {module_type : HelloWorld}
}
e1 : [ hi ]
e1 : [ ]
end_paths      : [ e1 ]

}

I observe that this configuration will run the module HelloWorld. If I reverse the order of the two definitions of e1, it will not run HelloWorld. So the rule appears to be that the first defintion wins, not the last. I expected the opposite.

History

#1 Updated by Rob Kutschke over 8 years ago

Here is a related issue.

process_name : fhiclTest00

physics : {

analyzers: {
hi : {module_type : HelloWorld}
}
e1 : [ hi ]
end_paths      : [ e1 ]

}

physics.analyzers.e1 : [ ]

This gives me a parse error:
terminate called after throwing an instance of 'cet::coded_exception<fhicl::error, &(fhicl::detail::translate(fhicl::error))>'
what(): ---- Can't find key BEGIN
physics.analyzers.e1.module_label -- not a table (at part "module_label")
---- Can't find key END

Aborted

#2 Updated by Walter E Brown over 8 years ago

  • Category set to Infrastructure
  • Status changed from New to Resolved
  • Assignee set to Walter E Brown
  • Target version set to 1.00.00
  • % Done changed from 0 to 100

#3 Updated by Christopher Green over 8 years ago

  • Subject changed from Is this a bug? to Is this a bug (diplicate key precedence reversed in nested context)?
  • Status changed from Resolved to Closed


Also available in: Atom PDF