Back Midas Rome Roody Rootana
  Rome Analyzer Framework  Not logged in ELOG logo
Entry  03 Apr 2005, Ryu Sawada, Suggestion, user defined command line options 
    Reply  22 Apr 2005, Ryu Sawada, Suggestion, user defined command line options 
       Reply  22 Apr 2005, Ryu Sawada, Suggestion, user defined command line options 
Message ID: 69     Entry time: 03 Apr 2005     Reply to this: 78
Author: Ryu Sawada 
Topic: Suggestion 
Subject: user defined command line options 
This is not strong request, just a proposal because the same thing can be done by configuration file.

It may be useful if users can have his command line options.

For instance.
<CommandOptions>
  <CommandOption>
    <OptionFlag>m<OptionFlag>
    <OptionName>isMC<OptionName>
    <OptionType>Bool_t<OptionType>
    <OptionInitialization>false<OptionInitialization>
  </CommandOption>
  <CommandOption>
    <OptionFlag>t<OptionFlag>
    <OptionName>TriggerType<OptionName>
    <OptionType>Int_t<OptionType>
    <OptionInitialization>0<OptionInitialization>
  </COmmandOption>
</CommandOptions>

Then user can change the variable with command line option like
./megframework -m -t 2;

Then builder creates new method.
(Bool_t) MEGAnalyzer::GetisMC()
(Int_t) MEGAnalyzer::GetTriggerType()
ELOG V3.1.4-2e1708b5