On Fri, Jun 15, 2018 at 12:22 PM, Janus Weil <ja...@gcc.gnu.org> wrote:
> Am 14. Juni 2018 12:40:19 MESZ schrieb Janne Blomqvist < > blomqvist.ja...@gmail.com>: > In Fortran, it still feels like functions as such are second-class > citizens. People seriously advise against using them. Doesn't really help > the attractivity of the language. Yes. Back when I followed c.l.f, several experts did advise people to never use functions unless they were pure (or more or less effectively so, if they didn't fulfill the standard requirements for purity). Considering that at least some of those same experts were also part of the Fortran standards committee, I just find it very strange that, to the best of my knowledge, no effort to fix this has been done. IMHO it is completely insane to optimize out impure functions, just for a > little bit of speedup, but sacrificing compiler-independent results. > > I really don't understand why I'm so alone here with this opinion. > I would agree with you if there were some substantial majority opinion among Fortran programmers that all the parts of a logical expression are always evaluated, contrary to what the standard actually guarantees. But as we have seen e.g. in the PR's that this patch attempt to fix, some people actually seem to assume short-circuiting, e.g. by writing code like a /= 0 .and. b/a > c or associated(t) .and. func(t) -- Janne Blomqvist
