eggs that are misusing the assert macro

[ckeen]

Recent changes enforce the msg argument of assert to be a string. This triggers an error in

* er-macros
* contracts
* tubles
* skiplists
* ugarit

For details see for example this salmonella report:
http://tests.call-cc.org/master/linux/x86/2012/03/07/salmonella-report/

I am attaching this to juergen since most of this are his, alaric in CC for ugarit...

[alaric]

Is it a misuse of assert to have an expression that generates a string as the message? I'd argue that this is a useful feature, to dynamically generate more informative assertion failure messages :-)

I have submitted a patch to chicken-hackers that would re-enable this; let's see if consensus is that assert needs to have a static string argument!