Curl Sonntag

My one reservation has been the use of a single identifier as the literal for constructing the parameterized class: I have tested and proposed a small change to the macro to accept a ClassName.classProp ( a BinaryOp "dot" expression) as a more easily documented item and as a more easily understood item - and easier to track than a single identifier in a macro call. Aside from that one reservation, Sonntag is a great showcase of what can be done by leveraging key features or Curl: macros, multiple inheritance, mixins and parameterized classes - and all on top of the default Curl events. This type of framework may be what is needed for maintenance of applications which must frequently respond to requests for change: designers can have confidence that they are able to test that a graphics change has not unwittingly impacted app logic because the framework readily reflects what both the change request/ legacy documentation says is/should be the case. In my proposed variant style, all commands and messages can be tracked (assuming compliance with the style.)