Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c    |    Meh, in C you gotta define EVERYTHING    |    243,242 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 241,385 of 243,242    |
|    rbowman to James Kuyper    |
|    Re: Nice way of allocating flexible stru    |
|    21 Oct 25 18:41:10    |
      From: bowman@montana.com              On Tue, 21 Oct 2025 06:17:21 -0400, James Kuyper wrote:              > On 2025-10-20 21:51, Janis Papanagnou wrote:       >> On 20.10.2025 20:36, rbowman wrote:       > ...>> I have converted F77 code from NOAA's public domain stuff to C.       >>>       >>> https://en.wikipedia.org/wiki/F2c       >>>       >>> The utility does indeed convert Fortran 77 to C code that will compile       >>> but it is barely human readable and nothing you would want to       >>> maintain.       >>       >> If the transformation is done correctly there's no reason to inspect       >> the details of the generated "C" code, or is it?       >       > I've used a system, I don't remember which one, where I found out that       > the default Fortran "compiler" was simply a script that ran f2c followed       > by compiling the resulting C code.              It was a Bell labs creation and their f77 'compiler' sort of created an IL       that was passed to the C compiler. Like making sausage it works great if       you don't look at the process. If you want readable C code you can modify,       not so great.              I haven't had a need to did into it but on Linux f77 gets passed to       gfortran and I think it all ultimately winds up in C++.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca