Silverfrost Forums

Welcome to our forums

Checkmate vs Release - Error not consistent

22 Apr 2021 6:11 #27606

In the following code, if compiled with Checkmate 32, the error is flagged. It is not flagged in Release 32. I did a quick check of the other Plato options. None of the other compile/link options flag the error.

The code was compiled as FIXED FORMAT, wide source.

        integer i
j       i = i + 1
        end

The 'J' in column 1 is in error; only checkmate 32 seems to pick it up. I know an 'i' will do the same. I suspect anything but a 'C' or '!' (or numbers) will also cause the compile error for /CHECKMATE, but not for /RELEASE.

I discovered this after deleting a section of code, and a 'J' was left in column 1 of a real statement. I compile as both /CHECKMATE and /RELEASE, and noticed the flagging.

23 Apr 2021 6:30 #27607

Bill

Can you check this. I can't reproduce this fault.

Are you using a command line or Plato?

Are you using an FTN95 configuration file?

23 Apr 2021 1:55 #27611

I originally found this while running on the command line, then ran this in Plato (what I posted). It is possible that there is a command line switch set incorrectly in , say, the Checkmate 64 since I don't use it often. That said, the command line running of the compiler uses the same basic switches, changing out only the /CHECKMATE for /RELEASE. All the line format options are definitely the same!

Here's a DropBox link to the Plato project. https://www.dropbox.com/t/TlFOZ1QdQjqNg750

23 Apr 2021 4:09 #27615

Bill

Your project settings include a significant number of command line options. Some of them are either redundant or not helpful.

The one that is causing the failure is /CFPP. I will make a note that this needs fixing.

I suggest that you start with the default options and only add those that you really need.

23 Apr 2021 10:35 #27620

Good point. This workspace I'm using is used for all problem reports, and so has 'morphed' over the years.

I'll clean it up.

Bill

26 Apr 2021 12:54 #27629

This failure has now been fixed for the next release of FTN95.

Please login to reply.