Hi Thomas, > if we add a warning, we should add it both for > > if (flag .and. func()) > > and for > > if (func() .and. flag) > > because the standard also allows reversing the test (which my > original test did).
well, I really don't want to warn for hypothetical problems. Since we currently do not apply such an optimization, we should not warn about it (unless you find any other compiler which actually does). Whether to add this optimization in the future is a different topic of course, and can still be discussed later. Cheers, Janus
