Which of the following is true about "strict" mode in Avaloq Script?

In Avaloq Script, "strict" mode serves the purpose of promoting better coding practices by catching common coding errors at runtime. When strict mode is enabled, it enforces certain constraints that help developers identify potential issues in their code, such as assigning values to undeclared variables or making calls to functions that do not exist. This increased level of scrutiny encourages developers to write cleaner and more reliable code, ultimately improving the overall quality of the software.

While the other options may seem plausible, they do not accurately represent the function of strict mode. It is important to recognize that strict mode is not the default mode and does not disable error messages, nor does it allow type coercion, which can lead to ambiguous behavior. By focusing on the behaviors enforced by strict mode, developers can avoid mistakes that could lead to unexpected results in their programs.