RE: initd ASSERTs

 
>hi Mats
>One thing that occurs to me is that the ASSERTS method used
>here is really for use with .m files as in the X Test suite
>where assert, strategy and code are maintained in a single
>file and there is a code generator.
>
>We might want to think of a convention for having the
>ASSERTS and Strategy inline in the source code and
>then extract them automatically to an asserts file.
>This way the code would be in sync with the assertions.
>For example
>
>  tet_infoline "ASSERT: this is assertion text..."
>
>  tet_infoline "STRATEGY: this is some strategy text"
>
>or some other convention
>
>tet_infoline "ASSERT: Reference..."
>tet_infoline "assertion text"
>tet_infoline "STRATEGY:"
>   ....
>
>we could probably code up some macros to do some of this..

I think this would be a good step forward, yes.