<?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 List-directed unformatted read problems in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100182#M126595</link>
    <description>&lt;P&gt;I was just reading jm-nichols post on some "old code" and unformatted reads and noted a similar problem I was having with somewhat similar code:&lt;/P&gt;

&lt;PRE class="brush:fortran;"&gt;REAL TIME
CHARACTER (LEN = 8) NAME
INTEGER IX, IY, IZ, IDX, ITYPE
! INPUT_CODE is an input parameter, the UNIT number
READ(INPUT_CODE,*) NAME, TIME, IX, IY, IZ, IDX, ITYPE&lt;/PRE&gt;

&lt;P&gt;I was getting a cold hard crash when the input stream had a forward slash in the name. &amp;nbsp;Are the admissible characters you can read into a character string with an unformatted READ documented somewhere? &amp;nbsp;Might this behavior have something to do with my compiler settings?&lt;/P&gt;</description>
    <pubDate>Tue, 08 Dec 2015 20:43:37 GMT</pubDate>
    <dc:creator>NotThatItMatters</dc:creator>
    <dc:date>2015-12-08T20:43:37Z</dc:date>
    <item>
      <title>List-directed unformatted read problems</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100182#M126595</link>
      <description>&lt;P&gt;I was just reading jm-nichols post on some "old code" and unformatted reads and noted a similar problem I was having with somewhat similar code:&lt;/P&gt;

&lt;PRE class="brush:fortran;"&gt;REAL TIME
CHARACTER (LEN = 8) NAME
INTEGER IX, IY, IZ, IDX, ITYPE
! INPUT_CODE is an input parameter, the UNIT number
READ(INPUT_CODE,*) NAME, TIME, IX, IY, IZ, IDX, ITYPE&lt;/PRE&gt;

&lt;P&gt;I was getting a cold hard crash when the input stream had a forward slash in the name. &amp;nbsp;Are the admissible characters you can read into a character string with an unformatted READ documented somewhere? &amp;nbsp;Might this behavior have something to do with my compiler settings?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 20:43:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100182#M126595</guid>
      <dc:creator>NotThatItMatters</dc:creator>
      <dc:date>2015-12-08T20:43:37Z</dc:date>
    </item>
    <item>
      <title>List directed technically is</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100183#M126596</link>
      <description>&lt;P&gt;List directed technically is formatted. List directed read into a character variable is notoriously unreliable, although quote marks may help.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 21:01:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100183#M126596</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2015-12-08T21:01:32Z</dc:date>
    </item>
    <item>
      <title>First, some terminology. This</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100184#M126597</link>
      <description>&lt;P&gt;First, some terminology. This is a list-directed formatted read, not unformatted. The Fortran standard indicates what is valid input for list-directed. though Intel Fortran is a bit more lenient. In the case you mention, read of an undelimited character value stops when a "value separator) is seen. &amp;nbsp;The value separators are slash, comma and blank (or tab in our implementation). Slash causes input termination, so that is probably why your reads fail.&lt;/P&gt;

&lt;P&gt;You can enclose the name string in quotes in the input to get around this, if the name has separators in it.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 21:07:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100184#M126597</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2015-12-08T21:07:59Z</dc:date>
    </item>
    <item>
      <title>Thank you.  Yes,</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100185#M126598</link>
      <description>&lt;P&gt;Thank you. &amp;nbsp;Yes, unfortunately I misnamed the topic. &amp;nbsp;What I was trying to point out was that there was not an explicit FMT given with the READ. &amp;nbsp;Thank you for the list of "value separators" and the workaround. &amp;nbsp;I will inform our UI team of the limitation. &amp;nbsp;I suppose then one other limitation might be unmatched quote marks?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Dec 2015 10:20:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100185#M126598</guid>
      <dc:creator>NotThatItMatters</dc:creator>
      <dc:date>2015-12-09T10:20:04Z</dc:date>
    </item>
    <item>
      <title>Unmatched quotes would be a</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100186#M126599</link>
      <description>&lt;P&gt;Unmatched quotes would be a problem, yes.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Dec 2015 17:49:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/List-directed-unformatted-read-problems/m-p/1100186#M126599</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2015-12-09T17:49:06Z</dc:date>
    </item>
  </channel>
</rss>

