forums.silverfrost.com

[offthechart]

John C. I intentionally created the errors to check compiling! I realize there should not be .. in the do statement. /brief cures the problem. Without it, the command window does not give line numbers for errors. My previous post of yesterday explains the solution with creation a .CFG file that listed all source code with errors (in filenam.lis) displayed following the incorrect code statement.

[offthechart]

Yes John Silver. I removed both options you noted and the compile error line number did show up in the Command window. The only option in my .cfg file was reduced to /BRIEF However without /BRIEF, the line number does not show up in the Command window. Oh well. I am quite satisfied I have a working method to obtain useful error messages. Thanks for the inputs.

[JohnCampbell]

[mecej4]

I agree with John C's comment, with one caveat: the next-to-zero chance that Offthechart's licensed version of FTN95 7.0 hides line numbers whereas the personal versions of 6.35, 7.0, 7.2 and 8.62 that I used do not hide line numbers.

[offthechart]

OK gang, here goes for the last time. For whatever &^$^* reason, /ftn95 filename.f in my command window does not show error line numbers. I am not an unobservant idiot. As a previous long time analyst in the defense world and member of the Triplenine society, not much gets by me.

Get it? I don't know why, but that is what occurs when I compile. When I add /BRIEF line numbers show up in the command window. Great. When I create a ftn95.cfg file with /LIST included I get a full source file printout (filename.lis) with the error message following each errant statement. Excellent. I don't have the slightest idea about the inner workings of the maze named Silverfrost, but in general I am quite pleased with it.

I do not have a licensest version as I only create code at home when the desire strikes me. For example, a retired math friend wished to solve polynomial equations with complex coefficients. I discovered the Laguer method and successfully coded it. Or a barroom question: I wonder how much farther a home run travels in Denver versus San Francisco? Having discovered Internet data on drag and lift (Magnus) coefficients, off I went into the land of numerical integration. Keeps my 75 year-old mind working. Thanks for help y'all.

[JohnCampbell]

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.

[offthechart]

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

[offthechart]

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'. !!