home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.fortran      Putting John Backus on a giant pedestal      5,127 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 5,089 of 5,127   
   David Brown to Thomas Koenig   
   Re: "Internationalis(z)ing Code - Comput   
   05 Feb 26 11:13:07   
   
   XPost: comp.lang.c++   
   From: david.brown@hesbynett.no   
      
   On 05/02/2026 08:23, Thomas Koenig wrote:   
   > Lynn McGuire  schrieb:   
   >> On 2/4/2026 1:20 PM, Thomas Koenig wrote:   
   >>> Lynn McGuire  schrieb:   
   >>>   
   >>>> I am swinging huge datasets for simulation models from 1 MB to 1,000 MB.   
   >>>>     Nothing besides C++ has the oomph and speed to make this happen.   
   >>>   
   >>> Speed differences between compiled languages are reltively small.   
   >>> But Fortran (where I am reading this) can certainly do so.  A pity   
   >>> you missed out on Fortran's development in the last 35 years.   
   >>   
   >> We will see.   
   >   
   > We will not see, because you made the decision to switch to C++   
   > instead of gradually introducing modern Fortran features in your   
   > code.  There will be no benchmark to test against.   
   >   
      
   There would probably be speed improvements in simply converting from old   
   Fortran to re-written old Fortran - most re-writes offer plenty of scope   
   for improving the structure and algorithms of old code simply because   
   you have better knowledge of the real-world usage of the code, and you   
   can turn old "layers of patches and modifications" code into more   
   streamlined code.  Then there are more modern editors, linters,   
   debuggers, etc., that let you write code in different ways (without   
   losing track of what you are doing) than you could with ancient tools.   
   Then there are more modern compilers that do a much better job of   
   optimisation, especially tuning for running on more modern processors.   
   And you can re-write the code with a view to efficiency on modern   
   processors (such as by different choice of data types, consideration of   
   cache, etc.).  All that comes before using a more modern language standard.   
      
   Without knowing anything about the code, the company, the programmers,   
   the future plans, etc., it is totally impossible for others to guess if   
   a re-write to C++ or modern Fortran would be best - I assume that Lynn   
   and colleagues have that knowledge and made the best choice.  But I   
   would be confident that speed comparisons from a re-write in C++ to the   
   old Fortran code would not give a fair comparison of the languages here.   
      
   --- 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