UI functions argument type checks

[GoogleCodeExporter]

To improve the error feedback for users, the (or only some?) UI library
functions should check the types of expected arguments before performing any
other action. The reason for such checks is, that errors are detected as early
as possible, such that common Scheme editors can raise a proper exception at
the place where an erroneous function call actually happened. Another reason
are possible issues with side effects taking place in functions before the type
error of an argument is detected. It would be good, if erroneous function calls
because of wrong argument types never change the state of the RACR system.
Note, that it should be possible to statically activate or deactivate argument
type checks (using for example macros). If deactivated, there should be no
runtime overhead because of argument type checks (including any overhead for
checking if argument type checks have to be performed or not!).

Original issue reported on code.google.com by Christoff.Buerger on 28 Jun 2012 at 9:05

• Merged into: avoidance of inconsistent states in case of errors #31

[GoogleCodeExporter]

Note: Adding UI functions argument type checks would also attenuate the
inconsistent state problem when RACR exceptions are thrown (see issue #8).

Original comment by Christoff.Buerger on 18 Jun 2013 at 12:06

[GoogleCodeExporter]

The issue is refined and covered by issue #31.

Original comment by Christoff.Buerger on 13 Mar 2015 at 1:45

• Changed state: Duplicate