Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Visual Fortran 10.1 belongs to Fortran 2008?

johntm
Beginner
‎06-30-2008 06:28 PM
547 Views

Hi.My name isJohn.

This year,I got into master course and first became familiar with Fortran.

Yesterday, I got a question from a seniorwhether Visual Fortran 10.1 belongs to Fortran 2008 or 2005 or 2000.

He said there are two lines for Fortran version, one from product seller and the other one from US strandard.

Is there anyone who has any idea about the question?

0 Kudos

Link Copied

2 Replies
TimP
Honored Contributor III
‎06-30-2008 11:03 PM
547 Views
If you're talking about Fortran standards, the current one is known as Fortran 2003, and the previous one as Fortran 95. With correct choice of options, ifort is intended to implement all of f95, and much of f2003, including the TR options which came before 2003. Much the same is true of several other Fortran compilers. Fortran 2008 hasn't yet become a standard.
Are you confused by Microsoft Visual Studio release designations? Recent ifort 10.1 releases are compatible with VS2008 as well as VS2005, and, where applicable, VS2003, but those have no relationship to Fortran standards.
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎07-01-2008 06:05 AM
547 Views
Please see this support article.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.