Re: fortran 2003 compiler

On Mar 2, 8:21 am, "Tobias Burnus" <bur...@xxxxxxxx> wrote:

I think all Fortran compiler vendors to plan to fully support Fortran
2003, it only takes time.

That is not true, I am afraid. I think Salford/Silverfrost and Lahey/
Fujitsu for Windows are in maintenance mode. Someone recently wrote
here that

"According to one of their representatives that I communicated with
recently, Lahey is getting out of the Windows compiler business."

I would bet against a Lahey/Fujitsu Fortran 2003 compiler on any
platform, because they would want to amortize an investment in
developing a Fortran 2003 compiler over as many platforms as possible.

For some projects such as gfortran it depends on interest of a
developer (all do it in their spare time); their interest can be
directed by popular demand and by the number of other compilers which
support this feature. (Popular demand and many competing compilers
which support a given feature also speeds up the development for
commercial compilers.)

None of the gfortran developers are interested enough in Windows to
produce Mingw gfortran binaries in a timely manner, as Doug Cox does
for g95. Nor do I see instructions on the Gfortran wiki on how to
build the compiler from source. I will be reluctant to submit reports
against an obsolete version of the compiler.

For some Windows Fortranners, the ability to create GUI programs using
g95 or gfortran using something similar to Quickwin for DVF/CVF/IVF (I
think Absoft, Lahey, and Salford have analogous facilities) is more
important than F2003 features. I doubt the developer(s) of g95 and
gfortran want to invest their time in assisting Windows-only GUI
development. I wonder how many man-years it would take to develop
something like Quickwin for g95 and gfortran (I would want it to work
on both). I'd be willing to pitch in some money to pay a developer.

.

Relevant Pages

  • Re: hmm..interesting
    ... I used to be a professional software developer on both Unix/Linux (all ... flavours) and Windows (writing CFD and Valve-train dynamics software, ... the fact that Visual Studio allows you to get away with fairly sloppy ... difficult to find a C compiler that *doesn't* have vendor-specific ...
    (comp.sys.acorn.hardware)
  • Re: fortran 2003 compiler
    ... Fujitsu for Windows are in maintenance mode. ... I would bet against a Lahey/Fujitsu Fortran 2003 compiler on any ... None of the gfortran developers are interested enough in Windows to ... I'd be willing to pitch in some money to pay a developer. ...
    (comp.lang.fortran)
  • Re: A few quick questions about gfortran under cygwin
    ... >> Downloaded the windows version and it actually works - sort of. ... >> Gfortran did compile about 6k lines of that I threw at it. ... "pretty much anything anyone tries to throw at the compiler". ...
    (comp.lang.fortran)
  • Re: gfortran 2007 annual report
    ... On Windows, you probably mean. ... I use gfortran as a native 64 bit ... compiler on GNU/Linux AMD64 now for about 2.5 years. ... but that is pretty common in old fortran source. ...
    (comp.lang.fortran)
  • Re: fortran 2003 compiler
    ... Fujitsu for Windows are in maintenance mode. ... I would bet against a Lahey/Fujitsu Fortran 2003 compiler on any ... Nor do I see instructions on the Gfortran wiki on how to ... I'd be willing to pitch in some money to pay a developer. ...
    (comp.lang.fortran)