<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Fortran Interface compilation Question in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669148#M175121</link>
    <description>&lt;P&gt;In an earlier post regarding to Fortran Module Wizard there are some warnings produced by the IFX &amp;amp; IFORT compilers. The example below is typical of a case where compiler issues a warning:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Modules\MSPPT.f90(8333): warning #6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value. [NEWSECTIONINDEX]&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="fortran"&gt;  			SUBROUTINE $Presentation_NewSectionAfter($OBJECT, Index, AfterSlide, sectionTitle, newSectionIndex, $STATUS)
				!DEC$ ATTRIBUTES DLLEXPORT	:: $Presentation_NewSectionAfter
				IMPLICIT NONE
	
				INTEGER(INT_PTR_KIND()), INTENT(IN)	:: $OBJECT	 ! Object Pointer
				!DEC$ ATTRIBUTES VALUE	:: $OBJECT
				INTEGER, INTENT(IN)	:: Index	
				!DEC$ ATTRIBUTES REFERENCE	:: Index
				LOGICAL(2), INTENT(IN)	:: AfterSlide	
				!DEC$ ATTRIBUTES REFERENCE	:: AfterSlide
				CHARACTER(LEN=*), INTENT(IN)	:: sectionTitle	! BSTR
				INTEGER, INTENT(OUT), VOLATILE	:: newSectionIndex	
				!DEC$ ATTRIBUTES REFERENCE	:: newSectionIndex
				INTEGER(4), INTENT(OUT), OPTIONAL	:: $STATUS	 ! Method status
				!DEC$ ATTRIBUTES REFERENCE			:: $STATUS
				INTEGER(4) $$STATUS
				INTEGER(INT_PTR_KIND()) invokeargs
				invokeargs = AUTOALLOCATEINVOKEARGS()
				CALL AUTOADDARG(invokeargs, '$ARG1', Index)
				CALL AUTOADDARG(invokeargs, '$ARG2', AfterSlide)
				CALL AUTOADDARG(invokeargs, '$ARG3', sectionTitle, AUTO_ARG_IN, VT_BSTR)
				CALL AUTOADDARG(invokeargs, '$ARG4', newSectionIndex, AUTO_ARG_OUT)
				$$STATUS = AUTOINVOKE($OBJECT, 2090, invokeargs)
				IF ($$STATUS == DISP_E_EXCEPTION) CALL $$DisplayError(invokeargs)
				IF (PRESENT($STATUS)) $STATUS = $$STATUS
				CALL AUTODEALLOCATEINVOKEARGS (invokeargs)
			END SUBROUTINE $Presentation_NewSectionAfter
  &lt;/LI-CODE&gt;&lt;P&gt;The argument flagged up has the VOLATILE attribute. Why does the compiler issue the warning inside an interface definition when INTENT(OUT) arguments are never given an explicit value? Is this a compiler bug or am I not fully understanding the situation?&lt;/P&gt;</description>
    <pubDate>Sun, 23 Feb 2025 15:36:22 GMT</pubDate>
    <dc:creator>Stephen_Sutcliffe</dc:creator>
    <dc:date>2025-02-23T15:36:22Z</dc:date>
    <item>
      <title>Fortran Interface compilation Question</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669148#M175121</link>
      <description>&lt;P&gt;In an earlier post regarding to Fortran Module Wizard there are some warnings produced by the IFX &amp;amp; IFORT compilers. The example below is typical of a case where compiler issues a warning:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Modules\MSPPT.f90(8333): warning #6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value. [NEWSECTIONINDEX]&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="fortran"&gt;  			SUBROUTINE $Presentation_NewSectionAfter($OBJECT, Index, AfterSlide, sectionTitle, newSectionIndex, $STATUS)
				!DEC$ ATTRIBUTES DLLEXPORT	:: $Presentation_NewSectionAfter
				IMPLICIT NONE
	
				INTEGER(INT_PTR_KIND()), INTENT(IN)	:: $OBJECT	 ! Object Pointer
				!DEC$ ATTRIBUTES VALUE	:: $OBJECT
				INTEGER, INTENT(IN)	:: Index	
				!DEC$ ATTRIBUTES REFERENCE	:: Index
				LOGICAL(2), INTENT(IN)	:: AfterSlide	
				!DEC$ ATTRIBUTES REFERENCE	:: AfterSlide
				CHARACTER(LEN=*), INTENT(IN)	:: sectionTitle	! BSTR
				INTEGER, INTENT(OUT), VOLATILE	:: newSectionIndex	
				!DEC$ ATTRIBUTES REFERENCE	:: newSectionIndex
				INTEGER(4), INTENT(OUT), OPTIONAL	:: $STATUS	 ! Method status
				!DEC$ ATTRIBUTES REFERENCE			:: $STATUS
				INTEGER(4) $$STATUS
				INTEGER(INT_PTR_KIND()) invokeargs
				invokeargs = AUTOALLOCATEINVOKEARGS()
				CALL AUTOADDARG(invokeargs, '$ARG1', Index)
				CALL AUTOADDARG(invokeargs, '$ARG2', AfterSlide)
				CALL AUTOADDARG(invokeargs, '$ARG3', sectionTitle, AUTO_ARG_IN, VT_BSTR)
				CALL AUTOADDARG(invokeargs, '$ARG4', newSectionIndex, AUTO_ARG_OUT)
				$$STATUS = AUTOINVOKE($OBJECT, 2090, invokeargs)
				IF ($$STATUS == DISP_E_EXCEPTION) CALL $$DisplayError(invokeargs)
				IF (PRESENT($STATUS)) $STATUS = $$STATUS
				CALL AUTODEALLOCATEINVOKEARGS (invokeargs)
			END SUBROUTINE $Presentation_NewSectionAfter
  &lt;/LI-CODE&gt;&lt;P&gt;The argument flagged up has the VOLATILE attribute. Why does the compiler issue the warning inside an interface definition when INTENT(OUT) arguments are never given an explicit value? Is this a compiler bug or am I not fully understanding the situation?&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 15:36:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669148#M175121</guid>
      <dc:creator>Stephen_Sutcliffe</dc:creator>
      <dc:date>2025-02-23T15:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: Fortran Interface compilation Question</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669153#M175122</link>
      <description>&lt;P&gt;If you look at the interfaces&amp;nbsp; for AUTOADDARG in IFAUTO.f90 you will see the value arg has intent(in) therefore in the caller it cannot be a var that has intent(out). The error message is correct. The&amp;nbsp;&lt;SPAN&gt;newSectionIndex declaration I would suggest wrong.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 15:49:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669153#M175122</guid>
      <dc:creator>andrew_4619</dc:creator>
      <dc:date>2025-02-23T15:49:45Z</dc:date>
    </item>
    <item>
      <title>Re: Fortran Interface compilation Question</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669162#M175123</link>
      <description>&lt;P&gt;Thanks Andrew, these arguments appear to have been incorrectly created by the Fortran Module Wizard. In the earlier post we found other probable errors in the generated COM/Auto interface and variable definitions for the Powerpoint application.&lt;/P&gt;&lt;P&gt;I will check all such similar warnings in my PPT, Word &amp;amp; Excel COM interfaces to verify they match the definitions in ifauto and ifcom modules.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 16:39:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669162#M175123</guid>
      <dc:creator>Stephen_Sutcliffe</dc:creator>
      <dc:date>2025-02-23T16:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: Fortran Interface compilation Question</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669170#M175125</link>
      <description>&lt;P&gt;It may be the data structures in the Powerpoint com are incorrect in this case so Mod Wiz just did what it was told. I looked at&amp;nbsp;&lt;A href="http://underpop.online.fr/m/microsoft-powerpoint/help/presentation-newsectionafter-method.html.gz" target="_blank"&gt;http://underpop.online.fr/m/microsoft-powerpoint/help/presentation-newsectionafter-method.html.gz&lt;/A&gt;&amp;nbsp;which suggests it is intent(in).&lt;/P&gt;</description>
      <pubDate>Sun, 23 Feb 2025 17:11:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Interface-compilation-Question/m-p/1669170#M175125</guid>
      <dc:creator>andrew_4619</dc:creator>
      <dc:date>2025-02-23T17:11:55Z</dc:date>
    </item>
  </channel>
</rss>

