forums.silverfrost.com

[jcherw]

I am working with a large complex and somewhat dated program (developed between 1988 and 2006) moving it to 64 bits. Running checkmate x64 results in lots of stops on UNDEF variables. I started hand-coding initial values as appropriate, but that turns out to be a lot of work. I read about the /ZERO option, which however is not available for ftn95 64 bit.

Is anyone aware of a viable alternative for the /ZERO option in ftn95 64 bit? There are a lot of arrays (few 100) declared via allocate statements.

Is there a way to conduct a zeroise along with the allocate??

[PaulLaidler]

Variables that have the SAVE attribute are preset to zero. You can use /SAVE on the command line to give all local variables the SAVE attribute but this could make your executable very large.

/ZEROISE (for 32 bit applications) may not do what you may think it ought. It only has effect when used with /UNDEF and then it presets variables to zero rather than an undefined state that is used at runtime to detect undefined variables.

There is no way to combine "zeroise" with ALLOCATE but you can then set all of the elements of an array ARR to zero with the statement ARR = 0.

[John-Silver]

SUGGESTION for SF

What would be very useful in ftn95 would be, as well as flagging individual errors as they occur, to temporarily store them, and output them to an error file in groups.
In the current case that could take the form of listing all the UNDEFined variables per routine MODULE or (SUBROUTINE or FUNCTION) in alphabetical order, even setting each to zero.
That would make any case like this one much easier for the user to tackle.
The task of initialising hundreds of variables is not difficult but daunting in terms of the data to be typed !!!
_________________
''Computers (HAL and MARVIN excepted) are incredibly rigid. They question nothing. Especially input data.Human beings are incredibly trusting of computers and don't check input data. Together cocking up even the simplest calculation ... "

[PaulLaidler]

When an undefined variable is encountered (at runtime) an exception is raised and the application terminates. So you can only get one at a time.

[PaulLaidler]

I will have to check the details but it appears that 64 bit ALLOCATE automatically zeros the allocated memory unless /UNDEF (or an option like /CHECKMATE that implies /UNDEF) is used in which case the memory is initialised to the undefined state. This is not documented and may change.

[John-Silver]

[PaulLaidler]

You can only test conclusively for undefined values at runtime.
The compiler can and does provide a compile time warning in some contexts.