User-defined constructor issues with Intel Fortran about datetime-fortran HOT 7 CLOSED

The above issue can be reproduced with the following example:

module mymod
implicit none

type :: mytype
  private
  integer :: a
  contains
  procedure,private :: eq
  generic :: operator(==) => eq
endtype mytype

interface mytype
  module procedure :: constructor
endinterface mytype

contains

type(mytype) function constructor(a)
  integer,intent(in),optional :: a
  if(present(a))then
    constructor % a = a
  else
    constructor % a = 0
  endif
endfunction constructor

logical function eq(m0,m1)
  class(mytype),intent(in) :: m0
  class(mytype),intent(in) :: m1
  eq = m0 % a == m1 % a
endfunction eq

endmodule mymod

module wrapper_module
use mymod,only:mytype
endmodule wrapper_module

program test
use wrapper_module
implicit none

write(*,*)mytype() == mytype(0)

endprogram test

The code compiles and executes as expected if only:mytype is omitted from the use statement in the wrapper_module, but not otherwise. Filed this on Intel Fortran forums, currently pending.

from datetime-fortran.

https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/685085

from datetime-fortran.

It seems that replacing the specific use statements from the parent module, i.e.:

use mod_datetime, only:datetime,date2num,datetimeRange,daysInMonth,&
                       daysInYear,isLeapYear,num2date,strptime,tm2date
use mod_timedelta,only:timedelta
use mod_clock,    only:clock
use mod_strftime, only:tm_struct,c_strftime,c_strptime

with the general all-inclusive statements like:

use mod_datetime
use mod_timedelta
use mod_clock
use mod_strftime

makes ifort not complain anymore about binary operators not being defined. So, for some reason, when importing the datetime type from mod_datetime, ifort is unable to import the overloaded operators as well. I do not understand why. Happens with both v16 and v17. gfortran reports no issue at all. for the time being, will use the all-inclusive use statements because ifort needs them.

I am still not able to reproduce this behavior with a simpler example. Stay tuned.

from datetime-fortran.

Filed this on Intel Fortran forums, currently pending.

Link?

from datetime-fortran.

The issue remains as of 19.0.1.144 Build 20181018 on 64-bit Linux.

from datetime-fortran.

This issue should be resolved thanks to switching to single-module library in #69. Needs to be confirmed.

from datetime-fortran.

No issue with ifort 2021.1 Beta 20200602. Closing.

from datetime-fortran.