Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Where possible, edges connecting nodes are
given different colours to make them easier to distinguish in
large graphs.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Where possible, edges connecting nodes are
given different colours to make them easier to distinguish in
large graphs.
Source Code
impure elemental function ESMF_MeshEQ(mesh1,mesh2)!! !RETURN VALUE:logical::ESMF_MeshEQ! !ARGUMENTS:type(ESMF_Mesh),intent(in)::mesh1type(ESMF_Mesh),intent(in)::mesh2! !DESCRIPTION:! Test if both {\tt mesh1} and {\tt mesh2} alias the same ESMF Mesh! object.!!EOPI!-------------------------------------------------------------------------------ESMF_INIT_TYPEminit1,minit2integer::localrc1,localrc2logical::lval1,lval2! Use the following logic, rather than "ESMF-INIT-CHECK-DEEP", to gain! init checks on both args, and in the case where both are uninitialized,! to distinguish equality based on uninitialized type (uncreated,! deleted).! TODO: Consider moving this logic to C++: use Base class? status?! Or replicate logic for C interface also.! check inputsminit1=ESMF_MeshGetInit(mesh1)minit2=ESMF_MeshGetInit(mesh2)! TODO: this line must remain split in two for SunOS f90 8.3 127000-03if(minit1.eq.ESMF_INIT_CREATED.and.&minit2.eq.ESMF_INIT_CREATED)thenESMF_MeshEQ=mesh1%this.eq.mesh2%thiselseESMF_MeshEQ=ESMF_FALSEendif end function ESMF_MeshEQ