From: cross@spitfire.i.gajendra.net   
      
   In article <109ps4q$153je$1@dont-email.me>,   
   Arne Vajhøj   wrote:   
   >On 9/9/2025 12:26 PM, Dan Cross wrote:   
   >> In article <109o21i$g12m$1@paganini.bofh.team>,   
   >> Waldek Hebisch  wrote:   
   >>> [snip]   
   >>> Well, the contex is libgfortran, part of Fortran compiler.  It is   
   >>> supposed to work with 60 years old Fortran code.  Such code may need   
   >>> compatiblity features.   
   >>   
   >> This gets back to my original question: not all code in   
   >> libgfortran is created the same.  I doubt that 60-year old code   
   >> cares about doing inode number+device equality to determine   
   >> uniqueness of a file on a Unix system...particularly as Unix did   
   >> not exist 60 years ago.   
   >>   
   >> Some code _may_ need that.  My guess is that 99.99% wouldn't   
   >> care and you can hack it for now to make forward progress.   
   >   
   >I suspect it is a standard compliance thing.   
   >   
   >Fortran 77 standard says about open:   
   >   
   >   
   >If the file to be connected to the unit is not the same as the file to   
   >which the unit is connected....   
      
   Aha.  That's a good reason, then; but in that case, the easiest   
   solution is probably to build libgfortran with `-D_USE_STD_STAT`   
   or write a VMS-specific implementation for this functionality.   
      
   	- Dan C.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)