From 23e1aec20a5d46c5b745c76bf2363686b21803f3 Mon Sep 17 00:00:00 2001 From: Henrik Tidefelt Date: Sun, 13 Dec 2020 00:53:50 +0100 Subject: [PATCH] Use terminology 'evaluated parameter' when describing Evaluate --- chapters/annotations.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/annotations.tex b/chapters/annotations.tex index 1f60fbc2a..b09bf667a 100644 --- a/chapters/annotations.tex +++ b/chapters/annotations.tex @@ -340,7 +340,7 @@ \section{Annotations for Code Generation}\label{annotations-for-code-generation} In the case of multiple conflicting annotations it is handled similarly to modifiers (e.g., an \lstinline!Evaluate! annotation on the component declaration takes precedence). The annotation \lstinline!Evaluate! is only allowed for parameters and constants. -Setting \lstinline!Evaluate = true! for a structural parameter, means that its value must be determined during translation, similar to a constant. +Setting \lstinline!Evaluate = true! for a structural parameter, means that it must be an evaluated parameter (i.e., its value must be determined during translation, similar to a constant). For a normal parameter, it has no impact, and it is recommended to issue a warning (except when the parameter is normal due to dependency on a parameter with \lstinline!Evaluate = false!, as this could be a sign of intentional overriding of \lstinline!Evaluate = true!, see example below). For both structural parameters and constants, the model developer further proposes to utilize the value for symbolic processing. A constant can never be changed after translation, and it is normal for its value to be used for symbolic processing even without \lstinline!Evaluate = true!.