Some debug(...) guarded code in a module included, some not...

[Robert M. Münch]

I use debug(...) specifications on my code. My app works when compiled 
in debug mode.

When I compile in release mode and explicitly use:

debug = debugprints;

on module level, my understanding is, that the debug guarded code will 
be included. But, some debug guarded code is include and some not... 
which is very strange. Because I expected to have the code either in or 
out.

Did anyone saw such a behaviour in the past?

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster