On Mon, 2 Sep 2024 07:57:48 -0500, "Michael F. Stemper" <
[email protected]> wrote in <vb4coc$2rg60$
[email protected]>:
On 01/09/2024 20.39, Lynn McGuire wrote:
On 8/30/2024 4:38 PM, D wrote:
On Fri, 30 Aug 2024, Lynn McGuire wrote:
On 8/29/2024 11:01 AM, Jaimie Vandenbergh wrote:
On 28 Aug 2024 at 12:51:29 BST, "Graham" <[email protected]>
wrote:
On 28/08/2024 06:01, Titus G wrote:
On 27/08/24 22:10, Graham wrote:
1234567890 2234567890 3234567890 4234567890 5234567890 6234567890 >>>>>>> 7234567890 8234567890
I'll take the bait. Please explain your signature.
Nothing exciting, I'm afraid. 80 characters.
Should be 72, Shirley?
Cheers - Jaime
I have written a quarter of a million (SWAG) lines of Fortran in my
lifetime. If I never write another line I will be happy. But I will
write more Fortran next Tuesday. Converting it all to C++ cannot
come soon enough.
Lynn
Ahh... but isn't it true that C++ is only for nerds? All the cool kids
write rust these days!
Converting Fortran or C++ to Rust is non trivial. I have actually
considered it. Shoot, converting Fortran to C++ is non trivial.
I would guess that a straight translation of Fortran to C++ could be automated. However, there doesn't seem to be any point in it unless
you're going to make use of the object-oriented capabilities of C++.
Then, of course, you're looking at a complete refactoring, which would, indeed, be non-trivial.
f2c(1) can convert to C++.
However, I suspect it isn't that easy to end up with working code.
--
-v
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)