On 24/12/2010, at 3:15 AM, john skaller wrote:
>
> There are two other ways to treat failed requirements.
> A second mysterious way is: drop the symbol with the requirement silently.
> The sane way is: reject the program with a diagnostic.
Ok, this is actually not so easy. In the process of b
On 24/12/2010, at 3:15 AM, john skaller wrote:
>
> There are two other ways to treat failed requirements.
> A second mysterious way is: drop the symbol with the requirement silently.
> The sane way is: reject the program with a diagnostic.
Ok, this is actually not so easy. In the process of b
I'm playing with the requirements processing at the moment because I'm getting
confused by "isnan" being used by not sucking in the header file.
At present, failed requirements are simply ignored. Basically, if you require X
than all the X inserts are generated, but the set of such inserts can be
