<?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: Visual studio integration : new file dialog : case of name  in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865744#M70609</link>
    <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="margin-top: 5px; width: 100%;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/160574"&gt;Ronald Green (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;&lt;BR /&gt;I see your point - the Add New shows "Fortran File (.f90)" but by default it creates the file as "SourceX.F90". This is inconsistent and probably we should at a minimum make this consistent. And perhaps add an option to allow the default to be one or the other.&lt;BR /&gt;&lt;BR /&gt;Of course, Windows is case insensitive, so .F90 vs .f90 is irrelevant. HOWEVER, on Linux and Mac there is a big difference between the 2 file extensions. .F .F90 files tell the compiler to run the Fortran preprocessor (FPP) on the source file, where .f .f90 files do not get run through the preprocessor. For IVF, the preprocessor is explicitly OFF unless you specifically enable it in the Properties in VS, or on the command line invoke it via the /Qfpp option.&lt;BR /&gt;&lt;BR /&gt;Steve Lionel might have a definitive answer for why one would want .F90 over .f90, or vice versa on Windows. Since he is out for a few weeks I'll add this to a list of posts that he needs to review on his return. In the meantime, I'll get a feature request to make the Add New text match the default file extension.&lt;BR /&gt;&lt;BR /&gt;ron&lt;BR /&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;One problem I have had with that:our versioning tool mercurial is case sensitve because of Unix/Linux case sensitiveness. Ive had a lot of trouble because other users changed the extension from .F90 to .f90 afterwards and mecurial didnt recognized them any more...&lt;BR /&gt;&lt;BR /&gt;So a consistant .F90 or .f90 will be great.&lt;BR /&gt;&lt;BR /&gt;Markus</description>
    <pubDate>Tue, 07 Apr 2009 07:01:36 GMT</pubDate>
    <dc:creator>onkelhotte</dc:creator>
    <dc:date>2009-04-07T07:01:36Z</dc:date>
    <item>
      <title>Visual studio integration : new file dialog : case of name extension</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865742#M70607</link>
      <description>When we create a new file in VS the new file dialog offers us choices of file types, all shown with lower case file extensions which is probably the most common useage. But the default file name given containes an upper case extension which I dont like and is inconsistent. I realise some people prefer upper case extensions so can we have an option setting for it?&lt;BR /&gt;&lt;BR /&gt;Andy Smith</description>
      <pubDate>Mon, 06 Apr 2009 08:36:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865742#M70607</guid>
      <dc:creator>Andrew_Smith</dc:creator>
      <dc:date>2009-04-06T08:36:03Z</dc:date>
    </item>
    <item>
      <title>Re: Visual studio integration : new file dialog : case of name</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865743#M70608</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/99034"&gt;Andrew Smith&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;When we create a new file in VS the new file dialog offers us choices of file types, all shown with lower case file extensions which is probably the most common useage. But the default file name given containes an upper case extension which I dont like and is inconsistent. I realise some people prefer upper case extensions so can we have an option setting for it?&lt;BR /&gt;&lt;BR /&gt;Andy Smith&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;I see your point - the Add New shows "Fortran File (.f90)" but by default it creates the file as "SourceX.F90". This is inconsistent and probably we should at a minimum make this consistent. And perhaps add an option to allow the default to be one or the other.&lt;BR /&gt;&lt;BR /&gt;Of course, Windows is case insensitive, so .F90 vs .f90 is irrelevant. HOWEVER, on Linux and Mac there is a big difference between the 2 file extensions. .F .F90 files tell the compiler to run the Fortran preprocessor (FPP) on the source file, where .f .f90 files do not get run through the preprocessor. For IVF, the preprocessor is explicitly OFF unless you specifically enable it in the Properties in VS, or on the command line invoke it via the /Qfpp option.&lt;BR /&gt;&lt;BR /&gt;Steve Lionel might have a definitive answer for why one would want .F90 over .f90, or vice versa on Windows. Since he is out for a few weeks I'll add this to a list of posts that he needs to review on his return. In the meantime, I'll get a feature request to make the Add New text match the default file extension.&lt;BR /&gt;&lt;BR /&gt;ron&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Apr 2009 20:45:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865743#M70608</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2009-04-06T20:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: Visual studio integration : new file dialog : case of name</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865744#M70609</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="margin-top: 5px; width: 100%;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/160574"&gt;Ronald Green (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;&lt;BR /&gt;I see your point - the Add New shows "Fortran File (.f90)" but by default it creates the file as "SourceX.F90". This is inconsistent and probably we should at a minimum make this consistent. And perhaps add an option to allow the default to be one or the other.&lt;BR /&gt;&lt;BR /&gt;Of course, Windows is case insensitive, so .F90 vs .f90 is irrelevant. HOWEVER, on Linux and Mac there is a big difference between the 2 file extensions. .F .F90 files tell the compiler to run the Fortran preprocessor (FPP) on the source file, where .f .f90 files do not get run through the preprocessor. For IVF, the preprocessor is explicitly OFF unless you specifically enable it in the Properties in VS, or on the command line invoke it via the /Qfpp option.&lt;BR /&gt;&lt;BR /&gt;Steve Lionel might have a definitive answer for why one would want .F90 over .f90, or vice versa on Windows. Since he is out for a few weeks I'll add this to a list of posts that he needs to review on his return. In the meantime, I'll get a feature request to make the Add New text match the default file extension.&lt;BR /&gt;&lt;BR /&gt;ron&lt;BR /&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;One problem I have had with that:our versioning tool mercurial is case sensitve because of Unix/Linux case sensitiveness. Ive had a lot of trouble because other users changed the extension from .F90 to .f90 afterwards and mecurial didnt recognized them any more...&lt;BR /&gt;&lt;BR /&gt;So a consistant .F90 or .f90 will be great.&lt;BR /&gt;&lt;BR /&gt;Markus</description>
      <pubDate>Tue, 07 Apr 2009 07:01:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865744#M70609</guid>
      <dc:creator>onkelhotte</dc:creator>
      <dc:date>2009-04-07T07:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: Visual studio integration : new file dialog : case of name</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865745#M70610</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt;Did Steve have time to look into this yet now he is back from his wonderful holiday?</description>
      <pubDate>Mon, 27 Apr 2009 09:40:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865745#M70610</guid>
      <dc:creator>Andrew_Smith</dc:creator>
      <dc:date>2009-04-27T09:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: Visual studio integration : new file dialog : case of name</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865746#M70611</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
I would think that lowercase .f90 would be preferable. I'll make a suggestion to the developers that the lowercase extension be used by default. &lt;BR /&gt;</description>
      <pubDate>Mon, 27 Apr 2009 13:33:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865746#M70611</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2009-04-27T13:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Visual studio integration : new file dialog : case of name</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865747#M70612</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
Here's how to fix this yourself. Find the "Intel Fortran" folder inside your Visual Studio install folder (Program FilesMicrosoft Visual Studio .NET 2003, Program FilesMicrosoft Visual Studio 8 or Program FilesMicrosoft Visual Studio 9.0.)&lt;BR /&gt;&lt;BR /&gt;Under "Intel Fortran" is a folder VFNewItems. In VFNewItems is a file NewItems.vsdir. Open this with Notepad. Find "Source.F90" and change it to read "Source.f90". Save and exit.&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Apr 2009 17:44:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865747#M70612</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2009-04-27T17:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Visual studio integration : new file dialog : case of name</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865748#M70613</link>
      <description>This was fixed in version 12.</description>
      <pubDate>Wed, 16 Feb 2011 20:15:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Visual-studio-integration-new-file-dialog-case-of-name-extension/m-p/865748#M70613</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2011-02-16T20:15:44Z</dc:date>
    </item>
  </channel>
</rss>

