forums.silverfrost.com

[DanRRight]

[mecej4]

If the statement numbered 24301 is within an IF...ENDIF block, you are not allowed to transfer to that statement from a location that is outside the IF block.

Please provide access to the full source code of the program unit in question, or at least show all the lines that contain "24301" as a label (statement or target of GOTO).

[LitusSaxonicum]

Dan,

The devilry that you so often encounter is probably the result of the satanic rituals implicit in your programming style.

A sprinkling of the following holy water may help:

Keep the subprograms short.

Use plenty of white space in your statements and in the subprograms as a whole.

Use statement numbers sparingly, and with a regular �stride� (say 10) through the program.

Use lots of comments.

Use short lines.

In WINIO@ calls, use few format codes.

Don�t include FORMAT statements adjacent to the READ or WRITE, instead, sequence them in a way that relates to what they do (e.g. 500 plus for READs, 600 plus for WRITEs) and put them in a bunch at the end of each routine.

Keep statements short by extracting common expressions yourself, instead of relying on the compiler to do it.

OK, some of these things might just increase run time, but that�s offset by making the incantation (sorry, Fortran) easier to read.

My religion also requires me not to use most of the blasphemy of Modern Fortran!

Eddie

[DanRRight]

Thanks mecej4 and Eddie for help and suggestions. Right now my assessment of the problem is that my file was somehow corrupted on massive, massive scale due to ... hell knows what.

As i have now no choice as to scale back to older variants, hopefully i will find on the way the actual place with an error otherwise i will post the offended subroutine with declarations and related functions.

Guessing was distortion of file because the RAM memory has no checksum, or my harddrives are now mostly flash based and hence more error prone, or Linux (and Windows under it) "sneezed"? I tortured it heavily last months, it was working with all its cores day and night, using all the memory and swap space, generating many terabytes of data. May be most reliable version of Linux is also needed, the RedHat, not Linux Mint (which has the best GUI interface and is the most user friendly but has its small problems too like all other Linux distros have but in general it's OK, at least it's better than Windows 10. The one major problem of Linux, specifically Ubuntu and related like Mint, is that it can be easily destroyed with what you download and install from the net, so you have to be careful by using only recommended software. Huge respect is for Android - my cell phones based on Android which based on Linux never had a single hiccup with 1000s installed programs in a decade. I would gladly switch on it, it will kill all other Linux distros eventially. Mint was losing twice in a year its graphics interface called GRUB, forcing to reboot )

[PaulLaidler]

Personally I don't believe that GIGOs are generally more active at the weekend unless that is when you do most of your programming.

[DanRRight]

Little who knows this secret. Weekends and holidays are special times for those who use supercomputers. And in older days mainframes. Often during these weekend couple days when computers complete (or end up in errors) most other users runs you could grab more CPU time for your own runs than in the entire week of other working days.I use this trick for 50 years

Another explanation for devilry is that on weekend when nothing disturbing you with the calls and emails you start thinking more broadly and try some new stuff. And all we know - as soon as we step just tiny turn out of some proven general path you immediately get a million of problems

There exist also third, funny reason. At some point 20 years ago i thought i am together with FTN95 so great at finding any errors in any codes -- the FTN95 with /undef was literally humiliating many programmers finding tons of errors in their codes -- that even label 666 will not do anything if i will use it. And all you now know what happened after that. Psychology hints that pride, hubris, arrogance are punishable. And so tell many religions, but i did not care because i am an atheist. But if think more the Fermi Paradox tells that what i call devilry actually is not impossible
/* Eddie - you have to add words about label use to your list

[DanRRight]

Paul, By the way, where is in Plato if/endif checking? I can not find it in menu. I expected it works like in Kate editor (in Kate it's a great realization but i suspect it has a bug there. Or in my code. But code works somehow)...

[PaulLaidler]

Plato provides highlighting for most Fortran constructs. This feature can be switched on from the Settings dialog that is accessed from the Tools menu.

Just go to the section marked "Miscellaneous" and check the appropriate box.

At the moment, highlighting does not work for named constructs.

[DanRRight]

Thanks. Plato works great, says no error.
Yea, i have to submit a bug report for Kate's if/endif checking. Lost two days on its devilry checking my devilry where the devil itself will break the leg. Otherwise it is great editor, very capable and stylish, i recommend. It's free by the way. Let's we all make it better by submitting to authors our bug reports and wishes.

[DanRRight]

Bug found.
I indeed transferred code flow into the location of IF/ENDIF block which had label 24301 but that was done hiddenly in the READ statement in case of error so that i did not pay attention many times looking into it being shocked with the massive corruption of the file:

[mecej4]

Dan, the following code extract illustrates the issue.

[DanRRight]

Who would expect editor has a bug? It hiccuped for the first time only on this piece of code.
Complicating also were that line 15624 was 10 miles after the offending line, the IF/ENDIF block contained 33 other IFs/ENDIFs and i am always in the hurry and always late .

Looks like i also misunderstood the Fortran rule about IF/ENDIF and the English of FTN95 with its error message. It sounded to me as contradicting reality and common sense: This label 24301 is inside IF/ENDIF block, hence it is used there, while compiler says it is used outside the IF/ENDIF block ! Pointing on offending READ statement with err=24301 is clearly needed.

I used heavily couple titles of software of British authors and i like both. What i do not like is their insistence on using words and manuals where showing examples would be much easier to the extent that the manuals and words would be completely redundant

[mecej4]

Ah, I see. Perhaps, if the error message had said "referenced" instead of "used" the meaning would have been clearer to you?

[DanRRight]

Mecej4, are you British ? Yes, "referenced" is better.

But not perfect.

Look at this file with my problem clearly exposed