Sujet : Re: xkcd: CrowdStrike
De : lynnmcguire5 (at) *nospam* gmail.com (Lynn McGuire)
Groupes : rec.arts.sf.written rec.arts.comics.stripsDate : 27. Jul 2024, 00:11:58
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v81ag0$31rgh$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : Mozilla Thunderbird
On 7/25/2024 5:03 PM, Scott Dorsey wrote:
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Is there a decent IDE for gnu fortran with gcc ? I tried Simply Fortran
and the debugger support is very minimal. I need to be able to stop on
the Xth call to a subroutine and Simply Fortran does not support that.
I have 5,000 subroutines (800k lines of F77), 300 common blocks, and
500K lines of C++ in over 10,000 files in my calculation engine.
Managing that without an IDE is challenging.
https://simplyfortran.com/
Eclipse might. To be honest I just use gdb for debugging outside of an
IDE. Used to love TotalView until it got too expensive (and I don't know
if it is even available for Windows).
My Hollerith is gone. My structures and unions are reduced. The code
actually converts to C++ fairly well until you get to the formats.
The older f2c used to do all the formatted I/O with a runtime library...
much the way most fortran implementations do.
--scott
I used gdb to debug x-windows and xview apps back in the early 1990s. The command line version kinda sucked.
Yeah, the formatted i/o from f2c really sucks. It converts the formats and writes into a series of executable statements using static memory images. I have seen one write statement translated into 30+ new statements. This is why I convert write statements by hand.
The real problem is that we have a Fortran interpreter embedded in our software. It uses a very primitive byte stream written in Fortran. However, it cheats on Formats and pipes them directly into a Fortran write statement.
Lynn