<?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 Re:Over-enthusiastic type declaration checking in array constructor implied do in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1385715#M161398</link>
    <description>&lt;P&gt;Issues #1 and #2 are fixed in the recent release of oneAPI version 2022.2. The ifort version is 2021.6.0.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 19 May 2022 18:40:37 GMT</pubDate>
    <dc:creator>Barbara_P_Intel</dc:creator>
    <dc:date>2022-05-19T18:40:37Z</dc:date>
    <item>
      <title>Over-enthusiastic type declaration checking in array constructor implied do</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1348245#M159130</link>
      <description>&lt;P&gt;Fortran 2018 introduced the capability to specify the type of the index in an implied do in an array constructor (i.e. an &lt;EM&gt;ac-implied-do&lt;/EM&gt; - F2018 R774 for syntax, F2018 19.4p5 for description of the relevant scope rules).&amp;nbsp; This appears in the documentation for the current oneAPI release (2022.1) - see &lt;A href="https://www.intel.com/content/www/us/en/develop/documentation/fortran-compiler-oneapi-dev-guide-and-reference/top/language-reference/data-types-constants-and-variables/variables-1/arrays/array-constructors.html" target="_self"&gt;here&lt;/A&gt;.&amp;nbsp; The compiler seems to know about this feature... but trips over subsequent silliness.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="fortran"&gt;PROGRAM ArrayConstructorWithTypeSpec
  IMPLICIT NONE
  INTEGER, ALLOCATABLE :: a(:)
  a = [(i, INTEGER :: i = 1, 10)]
  PRINT *, a
END PROGRAM ArrayConstructorWithTypeSpec
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="none"&gt;&amp;gt;ifort /check:all /warn:all /standard-semantics "2022-01-04 array-constructor.f90"
Intel(R) Fortran Intel(R) 64 Compiler Classic for applications running on Intel(R) 64, Version 2021.5.0 Build 20211109_000000
Copyright (C) 1985-2021 Intel Corporation.  All rights reserved.

2022-01-04 array-constructor.f90(4): error #6404: This name does not have a type, and must have an explicit type.   [I]
  a = [(i, INTEGER :: i = 1, 10)]
----------------------^
compilation aborted for 2022-01-04 array-constructor.f90 (code 1)&lt;/LI-CODE&gt;
&lt;P&gt;In the compilers documentation for array constructors (as linked above) - the expression provided for the assignment to C3 in one of the examples has a syntax error.&amp;nbsp; The &lt;FONT face="courier new,courier"&gt;INTEGER ::&lt;/FONT&gt; type spec is in the wrong spot - it can either go before the second opening parenthesis (specifies the type of the entire constructor) or after the first comma (specifies the kind of the ac-do-variable, as per the feature discussed above).&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="IanH_0-1641272461649.png" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/25276i19F76F42B2FED5E6/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="IanH_0-1641272461649.png" alt="IanH_0-1641272461649.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The example later for the extension where mixed real kinds are accepted also presumably has a syntax error (missing closing parenthesis).&lt;/P&gt;
&lt;P&gt;(Can those who prepare the downloadable html documentation (such as used for F1 help) please test things like the index on the Firefox browser - there are apparent attempts to use cross-origin objects that prevent the index and the like from functioning locally within that browser.)&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 05:17:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1348245#M159130</guid>
      <dc:creator>IanH</dc:creator>
      <dc:date>2022-01-04T05:17:05Z</dc:date>
    </item>
    <item>
      <title>Re:Over-enthusiastic type declaration checking in array constructor implied do</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1349105#M159199</link>
      <description>&lt;P&gt;Happy New Year!  This is a 3-fer, three bugs in one comment! &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;Let me look into these.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jan 2022 18:08:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1349105#M159199</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2022-01-06T18:08:26Z</dc:date>
    </item>
    <item>
      <title>Re:Over-enthusiastic type declaration checking in array constructor implied do</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1349140#M159205</link>
      <description>&lt;P&gt;An update for you...&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;I added your reproducer to an outstanding bug for what looks like the same issue.  Bug ID is CMPLRIL0-33539.  There is an awful workaround... remove the IMPLICIT NONE.&lt;/LI&gt;&lt;LI&gt;I filed DOC-9465 to correct the example in the Fortran Developer Guide and Reference.&lt;/LI&gt;&lt;LI&gt;Still waiting for a reply about the .html files.&lt;/LI&gt;&lt;/OL&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jan 2022 20:52:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1349140#M159205</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2022-01-06T20:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: Over-enthusiastic type declaration checking in array constructor implied do</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1349542#M159231</link>
      <description>&lt;P&gt;Now for issue #3... That's a known issue with Firefox. It's recommended that you use Chrome or Explorer. See the &lt;A href="http://05333700" target="_blank" rel="noopener"&gt;Fortran Developer Guide&lt;/A&gt;. There's a note on the main page.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 20:27:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1349542#M159231</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2022-01-07T20:27:04Z</dc:date>
    </item>
    <item>
      <title>Re:Over-enthusiastic type declaration checking in array constructor implied do</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1385715#M161398</link>
      <description>&lt;P&gt;Issues #1 and #2 are fixed in the recent release of oneAPI version 2022.2. The ifort version is 2021.6.0.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 May 2022 18:40:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Over-enthusiastic-type-declaration-checking-in-array-constructor/m-p/1385715#M161398</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2022-05-19T18:40:37Z</dc:date>
    </item>
  </channel>
</rss>

