forums.silverfrost.com

[StamK]

!ftn95$OPTIONS(-UNDEF)
used to work in 8.72, it now fails in 8.82 and 8.83.
I have to say that in the last version where it worked, it was not possible to do
!ftn95$OPTIONS(UNDEF)
later on for another section of the same file (to re-enable it basically).
But now it appears to be completely disabled.
Is this a deliberate or an accidental omission for the $OPTIONS keyword?

[PaulLaidler]

The ability to change the UNDEF state within a file was added fairly recently (perhaps following a request from you or your company). This turned out to be a mistake for 64 bits because FTN95 exports 64 bit object code in one chunk at the end of the compilation. This means that the UNDEF state cannot change between the "frontend" and the "backend" of FTN95.

In the current developers' version of 64 bit FTN95, one can change the default UNDEF state at the beginning of a file but not afterwards.

For 64 bits, if it becomes necessary to change the UNDEF state after the beginning of a file then that file must be split into two or more files each with its unique UNDEF state.

[StamK]

So basically in the new version of ftn95 (but not the current 8.83) we will be able to use the command !ftn95$OPTIONS(-UNDEF) at the beginning of a file, correct?

[PaulLaidler]

I don't recall what happens with 8.83 but it will be true for the next release.