forums.silverfrost.com

When compiled with /checkmate turned on (version 8.80), the following code gives a run-time error. "Reference through missing OPTIONAL argument".

(It worked fine with 8.70)

However, th ...

This test case is working now in 8.70.
Thanks Paul.

The following code will not compile with versions 8.61 or 8.66 when /ISO is used.

This is a short demonstration, extracted from a larger code where /ISO is required to ensure that SIZE returns a de ...

It looks like overflow is occurring with the argument to floor.

You have to be careful that the argument to floor is not outside the range of the largest default integer or the largest integer of a ...

Thanks Paul, your work on this is much appreciated.

I agree this would be a useful additional run-time check. Though it is the programmer's responsibility to check such things.

The NAG and gfortran compilers also detect the error with the (I4) forma ...

You can over-ride the function and count the calls using something like the following:

function sin(x)
real, intent(in) :: x
real sin
integer n
common /sin ...

It is possible to write tests as separate subroutines. With the right software (I use a python script that "understands" Fortran) you can automatically generate Fortran source code for a pr ...

See https://msdn.microsoft.com/en-us/library/windows/desktop/ms686774(v=vs.85).aspx regarding threads and stacks. Note the comments in the second paragraph regarding keeping stacks modest in size.

...

A well written program that confirms fully with the standard should be correct whether local variables are placed on the stack or in code space. In fact the Fortran standard does say anything about wh ...

When a local variable is declared it is usually put on the current stack frame.

You can use SAVE to over-ride this, or the use SAVE attribute for specific variables. If you don't want to change th ...

In the following code the associated() intrinsic incorrectly returns .TRUE. causing a run-time error when the deallocate statement is executed.

Since => null() initialisation is used the initial ...

Thanks. The same fix as before also applies to this code.

In v7.2, runtime checking was not applied when passing array sections as arguments. Runtime checking of array sections was added and worked ...

This bug is similar to the issue with passing automatic arrays on the other thread. A run-time error occurs on the line nn = n when /CHECKMATE or /CHECK is used with the 32 bit compiler. (v 8.3).

...

I find this thread very annoying.

As someone who uses SIZE with /64, I don't want an intrinsic that returns integer overflow. I want SIZE to return useful information.

How about catering to us u ...