forums.silverfrost.com

[PaulLaidler]

Thanks Ken. I will add it to the list.

[PaulLaidler]

ATAN(y,x) has now been added for the next release of FTN95.

[Kenneth_Smith]

Thanks Paul, I can see ATAN(y,x) is implemented in the latest download.

[JohnCampbell]

Paul,

I was trying to locate what features had been added to iso_fortran_env but could not find any documentation.

I wrote the following program to see what might come out.

I noted:
"integer_kinds" is not included ?
"iostat_end" /= -1 and "iostat_eor" not included
"numeric_storage_size" and "file_storage_size" not included

("int128" and "real80" are not in the standard, but I think "real128" is)

I think these are just constants so some may be an easy update and may help with documentation ?

[PaulLaidler]

Thanks John. I have made a note of your suggestion.

[PaulLaidler]

iso_fortran_env has been ammended for the next full release of FTN95.

The associated results for real_kinds and real80 relate to 64 bit FTN95 and are:

INTEGER,PARAMETER::REAL80=-1
INTEGER,PARAMETER::REAL_KINDS(2)=(/1,2/)

The values for 32 bit FTN95 are different from those provided by iso_fortran_env and are:

INTEGER,PARAMETER::REAL80=3
INTEGER,PARAMETER::REAL_KINDS(3)=(/1,2,3/)

[JohnCampbell]

Paul,

It is good to include in ISO_FORTRAN_ENV, those parameters that are relevant to FTN95 extensions for F03 and F08.

Just to clarify; I was checking if real80 or integer128 possibly might have existed. They are not in the standard, but should be listed in REAL_KINDS and INTEGER_KINDS if relevant.

It is a good change that "real_kinds" differ for 32 and /64

"integer_kinds" are in the standard and are an important report.

Thanks for these prompt updates.

John

( ps : have you considered including a /32 compile option ? )

[PaulLaidler]

John

read80 is -1 for /64 and for this value ISO_FORTRAN_ENV only gives the correct result for /64. This is because at the moment I can't think of a simple way to make read80 correct for both 32 and 64 bits.

read80 = -1 means that 80 bit reals are not available.

integer128 = -1 for both 32 and 64 bit FTN95.

If the compiler was configured by the user (via /config) to make /64 the default then /-64 would revert to the compiler default. In this context it might be helpful to have /32 as an alternative to /-64.

[PaulLaidler]

John

This issue has now been resolved. ISO_FORTRAN_ENV will give the relevant KINDs for both 32 bit and 64 bit FTN95.

/32 has been added as an alternative to /-64.

[JohnCampbell]

Paul,

Thanks for these changes.

I think that /32 is a good addition, especially for clearer documenting of compile options in my .bat builds.

Also, my test from Fri Nov 18 did not identify "integer_kinds" as being available. Hopefully I did not mis-spell.
Is it available ?

How does /ALT_KINDS work with these ?
( I see that "1.0_K must use the default KIND values"

I will test the next FTN95 version.

[PaulLaidler]

integer_kinds was missing and has been added for the next full release.

The KIND values in ISO_FORTRAN_ENV are the native KINDs, not the /ALT_KINDS values. They are constants that are external to the compiler. As things are, they don't change when /ALT_KINDS is used.

[PaulLaidler]

FTN95 has been extended so that in future ISO_FORTRAN_ENV will give the correct values for /ALT_KINDS.

[PaulLaidler]

z%re and z%im for complex z (from the 2008 Standard) has been added for the next release of FTN95.

[Kenneth_Smith]

Paul,
Thanks for implementing the 2008 Standard support for complex z. This will be very useful.
Ken

[PaulLaidler]

HYPOT has now been added to FTN95 and the DLLs for the next release.