forums.silverfrost.com

LitusSaxonicum · Posted: Tue Aug 13, 2019 10:42 am Post subject:

@John,

I think it's the /opt not the /p6 wot dun it; but reading up on what the P6 does, doesn't give me a lot of confidence. Core!

@Mecej4,

Just so we are on the same page, 1, seems to me to be a cause of the lack of robustness as defined by John, but 3. surely brings the code down every time, as I would expect 4. to also do. Improper integer expressions alternate 'coming right' with 'going wrong', and that should be obvious.

As for No. 2, why does that cause problems? Just asking.

Eddie

mecej4 · Joined: 31 Oct 2006 Posts: 1899

LitusSaxonicum · Posted: Tue Aug 13, 2019 3:56 pm Post subject:

Hi Mecej4,

Thanks for the explanation and the example.

Good, I'm safe from that one. I simply haven't got a clue what "j(1:9:2)" is or does*, as I'm no enthusiast for some code constructs.

Indeed, having the same variable twice in an argument list seems to me to be an incantation to summon up Dannian Devilry. Just call me old-fashioned.

Perhaps the abliity to spell and the adoption of certain restrictive rules on 'clever' constructs may be keeping some of us safe in ways we didn't realise.

But by the time I'd converted the example to Fortran that I can read and understand at a glance, the problem had gone away (and before you ask, fixed format, in capitals, removing parameters that don't do anything and constructs I never use, WRITE instead of print, a numbered FORMAT statement - and thank heavens you used implicit type so I was OK there!)

Eddie

*I worked it out for myself, after pondering briefly whether it meant 2,4,6 ... or 1,3,5... The fact that you can do certain things doesn't mean that you should, much less must.

PaulLaidler · Posted: Sat Oct 12, 2019 9:35 am Post subject:

I have discovered why this failure was not showing up on my machine. It is a bug and I have made a note that it needs to be fixed.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

It cannot be a case of using a different SALFLIBC.DLL, so I am curious to learn about the explanation.

PaulLaidler · Posted: Tue Oct 15, 2019 3:19 pm Post subject:

This bug has now been fixed for the next release of FTN95. The bug was restricted to the new functions erf, erfc, erfc_scaled, gamma, log_gamma, bessel_j0, bessel_j1, bessel_y0, bessel_y1, bessel_jn, bessel_yn.