OK ofthechart, here goes for the last time!

Can you:

generate a minimum reproducer: filename.f,

a .bat file that demonstrates the different performance which looks like below then

run the .bat to display the different error report formats,

attach the relevant files to help identify the problem.

dir > filename.tce
ftn95 filename.f 'bad options that omit the line numbers' /echo >> filename.tce
ftn95 filename.f 'good options that include the line numbers' /echo >> filename.trace
dir >> filename.tce

Could you also list the .bat, .tce and ftn95.cfg, or preferably include these in a .zip file, together with filename.f and best provide this as a lnk to dropbox or similar.

It would be best to provide filename.f as a link, so we can inspect the .f file for any unexpected characters that may be causing the problem (eg for unix or other non Dos/ansi characters)

I have already suggested a way of eliminating the error, should that be a useful way forward.

It would be good to get an explanation for this behaviour.

John

Hello JohnC. First I appreciate your knowledgable technical concern (and curiousity). Thinking upon the problem last night, there is a possible variable that affects the default error message 'problem'. I utilize a particular text editor for the creation and editing of most files, including Fortran source code. Of course, I have set up my editor to make editing life easier with various 'hot keys'. I have not utilized the specialized .F editing program that is available to create code.

I don't know if this is significant but my my understanding of Murphy's Law makes me suspicious. I could send you the source code text, but doubt it would be of value. ( I wrote it as a generic method for a friend who needed to know the response of a disk to intermittent torque pulses and the effects of static friction. It was up to him to modify it in any way for his particular purposes.)

Below is a file 'fvars.bat' that has existed on disk since I downloaded the compiler. I question its value to you also. Thanks.

@echo off echo. echo Setting Environment for FTN95 for Microsoft .NET and Win32 echo. SET PATH=C:\Windows\Microsoft.NET\Framework\v2.0.50727\;%PATH% SET PATH=C:\Program Files (x86)\Silverfrost\FTN95;%PATH% SET F95INCLUDE=C:\Program Files (x86)\Silverfrost\FTN95\Include SET MOD_PATH=C:\Program Files (x86)\Silverfrost\FTN95\Include

I did that. With an induced error I got in the command window:

*** unpaired right brackets 1 error [ <main program> ftn95/win32 v7.00.0] *** compilation failed

As usual, nothing more. It's only the .cfg file that gives me the correct line numbers help that is needed! At least I have a solution to the problem by using a .cfg file. When I use a .cfg file I get:

error C:\.............\filename.f 22: unpaired right brackets 1 error [ <main program> ftn95/win32 v7.00.0] *** compilation failed

Note the line number '22'. !!