<?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 No, that combination doesn't in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/protected-variables/m-p/1089178#M123764</link>
    <description>&lt;P&gt;No, that combination doesn't make sense, though I cannot find words in the standard prohibiting it. I would think that the combination should be allowed though the PROTECTED attribute would never come into play.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Apr 2017 20:06:40 GMT</pubDate>
    <dc:creator>Steve_Lionel</dc:creator>
    <dc:date>2017-04-21T20:06:40Z</dc:date>
    <item>
      <title>protected variables</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/protected-variables/m-p/1089177#M123763</link>
      <description>&lt;P&gt;This might be a stupid question, but does it make sense for a variable to be both PROTECTED and PRIVATE ?&amp;nbsp; I would have thought that PROTECTED variables are already PUBLIC.&amp;nbsp; For example, the following program would not compile unless the PROTECTED variable is explicitly made PUBLIC.&lt;/P&gt;

&lt;PRE class="brush:fortran;"&gt;module mymod
   integer,protected:: a = 1
   private
   !public a
end module mymod   
   
!------------------------------------------   
   
program test_public
   use mymod, only: a
   implicit none
   write(*,*) a
   stop
end program test_public
&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 17:40:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/protected-variables/m-p/1089177#M123763</guid>
      <dc:creator>Roman1</dc:creator>
      <dc:date>2017-04-21T17:40:33Z</dc:date>
    </item>
    <item>
      <title>No, that combination doesn't</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/protected-variables/m-p/1089178#M123764</link>
      <description>&lt;P&gt;No, that combination doesn't make sense, though I cannot find words in the standard prohibiting it. I would think that the combination should be allowed though the PROTECTED attribute would never come into play.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 20:06:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/protected-variables/m-p/1089178#M123764</guid>
      <dc:creator>Steve_Lionel</dc:creator>
      <dc:date>2017-04-21T20:06:40Z</dc:date>
    </item>
  </channel>
</rss>

