This repository has been archived by the owner on May 18, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 59
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This commit corrects the improper and inconsistent handling of parameters by implementing what is listed below: - Only evaluate structural parameters and parameters with annotation(Evaluate=true) during compile time by default. Final parameters and protected parameters are not evaluated any more. (see ticket:3211, ticket:4027) - Many different preOpt modules are merged to one preOpt module "evaluateParameters" with different flags instead -> To calculate additional parameters the following flags are introduced: --evaluateFinalParameters=<true|false> (default: false) --evaluateProtectedParameters=<true|false> (default: false) -> To activate/deactivate the replacement of the calculated parameters in the DAE use: --replaceEvaluatedParameters=<true|false> (default: true) - Mark structural parameters deciding the if-branch final (see ticket ticket:4053) - Structural parameters in instances are detected correctly (see ticket:4059) - Propagate the final attribute to parameters structural parameters depend on (see ticket:4052) - Mark parameters final if used for calculation of other parameters, because otherwise it leads to inconsistency when changing the value after compilation. Also replace the evaluated expressions because they are already evaluated and not changeable anymore. (see ticket:4027, ticket:3211) - Make final, structural and protected parameters unchangeable -> Write final parameters to _08bnd.c -> Make use of the isValueChangeable-flag (see ticket:4060, ticket:3211, ticket:4027)
- Loading branch information
1 parent
c2ed655
commit d75f648
Showing
9 changed files
with
501 additions
and
680 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.