#798: allow calculations in parameter assignments in parameter files --------------------------+------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: reopened Priority: optional | Milestone: Component: Cactus | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by knarf):
* status: closed => reopened * resolution: fixed =>
Comment:
I don't really like the notion of the ordering being important. Would it be a lot of work to first skip parameters which depend on values of other parameters and then continue assigning until all parameters are set or some are left which should produce an error (which would catch loops for instance)?