Summary
eggs that are misusing the assert macro
Metadata
- Id: 6510ebdff581df07a22b30e31b3bca5950e9aa41
- Trac id: 797
- Type: defect
- Reporter: ckeen
- Owner: juergen
- Cc: alaric
- Status: closed
- Component: extensions
- Estimated difficulty:
- Resolution: worksforme
- Priority: major
- Milestone:
- Version: 4.7.x
- Changetime: 2012-05-20 21:24:46 UTC
- Created: 2012-03-07 13:54:21 UTC
- Keywords: assert eggs macro
Description
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...
Changes and comments
[2012-03-12 17:44:13 UTC] alaric wrote:
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!