Context Navigation

Changes between Initial Version and Version 1 of Ticket #3717, comment 11

initial	v1
14	14	Btw. also the string valued solverMethod passed to `Clock(c, solverMethod)` is treated as sub-clock and checked for equality in `setSolverMethod`.
15	15
16		One might argue if the backend should compare parameter expressions for equality instead of comparing rational numbers / strings. I think that a forced evaluation in the frontend could be reverted once this will be needed and implemented.
	16	One might argue if the backend should compare parameter expressions for equality instead of comparing rational numbers / strings. Such a comparision would require expression simplification, alias elimination, sorting and the like. I think that a forced evaluation in the frontend could be reverted once this will be needed and implemented.
17	17
18	18	For the time being the backend fails if the parameters have not been evaluated. Modelica_Synchronous generally uses `Evaluate=true` annotations for these parameters, but not consistently because another tool forces the evaluation anyway.