name conflict between IFPORT and an object library

[Matthew_Nicoll]

I have an object library which has a function with the unfortunate name of "STAT".

I want to use the IFPORT module routine which also has the unfortunate name of "STAT".

How do I specify that the IFPORT STAT should be called, and not the object library STAT?

I tried the following statement:
  USE IFPORT, ONLY: File_Info => STAT
then calling File_Info, but that did not help.

(Is there a better way to get a file modification date in Windows than using STAT?)

[Steven_L_Intel1]

How about GETFILEINFOQQ?

The problem you have is that the actual portability routine is named STAT, so even if you hide the identifier the linker will still get the wrong one. That's a risk with the portability routines. I long for the days of VMS and its standards for keeping user and system namespaces separate.

[Matthew_Nicoll]

Thanks Steve.  GETFILEINFOQQ worked fine.