XPost: comp.lang.c++   
   From: tkoenig@netcologne.de   
      
   Lynn McGuire  schrieb:   
   > On 2/7/2026 1:15 PM, Thomas Koenig wrote:   
   >> Lynn McGuire  schrieb:   
   >>   
   >>> The only conversion problem that I am worried about is that I have   
   >>> Fortran 66 interpreter built into my software for my customers to write   
   >>> custom calculations embedded in their datasets attached to any type of   
   >>> object.  I will need to write a converter for the F66 format statements   
   >>> to C formats.   
   >>   
   >> I haven't used your software, but I have used Aspen (only very   
   >> little) and found it horrible.  How it is possible for a solution to   
   >> diverge when the starting solution is already converged is beyond   
   >> me, all explanations that occur to me could be considered insults,   
   >> so I am not toing to go into that.  That was worst; I hope your   
   >> software does better.   
   >>   
   >> But the F66 interpreter in Aspen was a close second; IIRC, it was   
   >> not even possible to declare variables. Argh.   
   > ...   
   >   
   > Huh, that does not make sense.  One needs variables to decomplicate   
   > complex calculations.  We even support common blocks in our F66   
   > interpreter user code so that variables can be stored from one iteration   
   > to the next.   
      
   You could use them via implicit typing, but you could not declare   
   them.  So, REAL A did not work (DIMENSION probably did).   
      
   Actually, the way I used them was mainly for a colleague who had   
   zero Fortran experience, and I got a few needed routines running.   
   More than 10 years ago)   
      
   --   
   This USENET posting was made without artificial intelligence,   
   artificial impertinence, artificial arrogance, artificial stupidity,   
   artificial flavorings or artificial colorants.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)