RE: [DUnit-interest] Interesting condition when "optimizations" i s turned on

[Larsson M. <Mar...@bk...>]

Mike asked:
>Are you suggesting here that you allow the code to compile 
> with hints <> 0 and warnings <> 0?  

I'm not suggesting anything of the sort, rather the opposite... :*)
This discussion originated with a question from Robert Dunn:

> I've noticed that if you don't set the result type of a boolean 
> function the Check function will not evaluate the condition 
> correctly.

I had a long reply with a lot of fun assembly code.
But I ended up suggesting eliminating hints and warnings.
That was after a lot of ugly (or fun) assembly, so I won't
blame anyone for not reading it.

Juancarlo suggested a quickfix by clearing AX.
Which won't work, I think. My assumption was that Robert 
really wanted to *test* if a method actually set it's 
returnvalue. That is not possible in anything but the 
simplest do-nothing methods.

M.


This footnote confirms that this email message has been swept by
our anti-virus solution for the presence of known computer viruses.
gfh-te-200*************************************************************