Joined: 29 Nov 2006
|Posted: Thu Apr 28, 2005 1:57 am Post subject: Salford FTN95: Fortran for Windows Version 4.80
|FTN95 version 4.80 is now available. The following is an overview of the changes and bug fixes between 4.70 and 4.80:
* NEW FEATURE: UNDEF array values in a MODULE are nolonger stored as static values.
* NEW FEATURE: ASSEMBLY_INTERFACE extended to allow pass by reference.
* NEW FEATURE: SLINK modified to make executables "Large address aware".
* NEW FEATURE: New comment embedded directives added (see help file).
* NEW FEATURE: UBOUND and SIZE can be used with .NET arrays.
* NEW FEATURE: /UNDEF applied to .NET NEW@ array.
The following is a summary of FTN95 bugs that have been fixed at version 4.8.
* Automatic DEALLOCATE (on exit from subprogram) not implemented for .NET.
* IO problem when OPEN follows OPEN on the same unit without intervening CLOSE.
* Regression. Blank lines after a comment causes error report line numbers to go wrong.
* /OPTIMISE problem when ASSIGN TO is used in a DO loop.
* ALLOCATE size is incorrect when calculated using INTEGER*1 variable arithmetic.
* Paricular application of MVBITS under .NET gives incorrect result.
* NET problem with MODULE procedure that has an internal function.
* Locked register problem with PRODUCT.
* Problem with open_wav_file_read@ when invalid file is encountered.
* IO is not initialised when READF@ called without prior OPEN etc.
* Foating point stack overflow problem. Incorrect assembly instruction under Win32.
* Problem with CSHIFT when used with /SAVE and /CHECKMATE.
* INTENT(INOUT) used with array passes incorrect address.
* False warning with INQUIRE and implied DO.
* NET problem with /DEBUG etc, too many members in TYPE causes access violation.
* NET problem with /CHECK and passing character variables to subprograms.
* False warning 133 with .NET and /CHECK.
* NET assignment of 2-dim .NET array element to variable does not work.
* NET assignment of character variable to string does not work when string is an argument in a subprogram.
* VAX style DATA list does not work for CHARACTER variables.
* Regression. Problem with CODE command when full stop is the first character in an assembly comment.
* ENTRY point problem under .NET when using /UNDEF.
* False warning with logical IF statement.
* FCORE4 failure at runtime when using /CHECK.