When config file does not set parameters, methods from other modules are not availble to Config.pm in object creation

[Felipe Figueiredo]

When parameters are used from the default, instead of read from the local config file, methods from Mosquito.pm, Traps.pm, etc. are not available to Config.pm when it creates a new config object. This causes problems in some cases for Config::read_*_file methods.

Correct calling order and make sure all methods are available to these Config.pm methods.

[Felipe Figueiredo (philsf)]

Need to check if this is really a bug.

[Felipe Figueiredo (philsf)]

It is, indeed, a bug. When default attributes from Mosquito.pm and Trap.pm are not read from the config file, they are not set in the Config->params attribute, and thus are not availble early enough to be called, for example, from MMRRSim::log_header().

[Felipe Figueiredo (philsf)]

A simple work-around this issue is to simply uncomment the parameters in the default config file. This would make all default values defined when the config file is checked.

[Felipe Figueiredo (philsf)]

Solution from IRC (ref to Moose::Manual::Attributes): remove default values from Mosquito.pm and Trap.pm, and store them in Config.pm (similarly to what's done in TRepid).

[Felipe Figueiredo (philsf)]

A regression detected when config file is not present, because read_config_file() returns too soon to get the default values was fixed in branch lp:~philsf/mmrrsim/fix-lp-1260621. Go back here and finish getting/setting the defaults for the other two classes: MMRRSim.pm and GridCell.pm, as defined in the config file.