default values of keyword parameters are not checked to be in the allowed set

[Roland Haas]

Currently neither the CST nor the runtime code stops a simulation if the default value of a parameter is not in the allowed set of values. The runtime code actually detects this state then outputs an (invisible since the info level is not yet available) warning about which parameter is affected, then another one to the effect of “but continuing anyway”.

It seems better if default values were restricted to be in the allowed range, ideally both at compile time and at runtime (in case compile time checks miss something).

[Roland Haas]

To be addressed after ET_2020_05

[Roland Haas]

Issue #2593 was marked as a duplicate of this issue.

[Steven R. Brandt]

On looking into this, I see that there are some serious bugs here. Working on a fix.

[Steven R. Brandt]

PR https://bitbucket.org/cactuscode/cactus/pull-requests/138/get-range-checking-working-for-parameters

[Roland Haas]

Has there been progress on this? The PR ends with a comment (by me) saying that keyword parameters are not checked to be in range and show the same issue so the pull request is incomplete. Similarly most likely for strings.

[Roland Haas]

Please apply.

[Roland Haas]

Applied as git hash ae667096 "Cactus: Get range checking working for parameters" of cactus