- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
Andy Smith
Andy Smith
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Andrew Smith
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?
Andy Smith
Andy Smith
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.
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.
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.
ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Ronald Green (Intel)
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.
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.
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.
ron
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...
So a consistant .F90 or .f90 will be great.
Markus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did Steve have time to look into this yet now he is back from his wonderful holiday?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.)
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was fixed in version 12.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page