forums.silverfrost.com

DanRRight · Posted: Thu Apr 24, 2014 11:59 am Post subject: /NO_TRUNCATE

Compiler produces wrong diagnostics error complaining about hitting the limit

*** Line is longer than 72 characters (because of /NO_TRUNCATE)

with completely legitimate Fortran line of exactly 72 or 132 characters long.

PaulLaidler · Posted: Thu Apr 24, 2014 3:23 pm Post subject:

OK. Thanks.

PaulLaidler · Posted: Thu Apr 24, 2014 7:35 pm Post subject:

This has now been fixed for the next release.

DanRRight · Posted: Fri Apr 25, 2014 4:35 pm Post subject:

Thanks

DanRRight · Posted: Mon Sep 08, 2014 1:11 am Post subject:

Paul,
Well, the no_truncate still has problems in 7.1

It still wrongly treats an exclamation mark after 72 positions as an error,
but worst of all it treats the line continuation hack in clearwin.ins as an error too

2/0011) INTEGER*4 CURSOR_ARROW,CURSOR_IBEAM,CURSOR_WAIT,CURSOR_CROSS, &
*** Line is longer than 72 characters (because of /NO_TRUNCATE) (In include
file C:\Program Files (x86)\Silverfrost\FTN95\include\CLEARWIN.INS)

So the code does not compile yet. But even if it still failed to work it found one error. When it will work this should be powerful bug pesticiding option

PaulLaidler · Posted: Mon Sep 08, 2014 8:31 am Post subject:

OK. I will log this for further investigation.

PaulLaidler · Posted: Fri Jan 16, 2015 11:01 am Post subject:

This issue has now been fixed for the next release.

DanRRight · Posted: Sun Jan 18, 2015 11:39 am Post subject:

Thank you very much. This is very useful to kill a bug or two. Bet everyone has truncation bugs

Just today i remembered that when tried if it was already fixed or not. Just to doublecheck: was also the error compiler reported in Clearwin.ins include file fixed if /no_truncate was used?

PaulLaidler · Posted: Sun Jan 18, 2015 5:04 pm Post subject:

I have just tried it on a fixed format file that has INCLUDE <windows.ins> and it works fine.