This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gfortran error format (was: Re: Emacs and GFortran)

From: Paul Thomas <paulthomas2 at wanadoo dot fr>
To: François-Xavier Coudert <fxcoudert at gmail dot com>
Cc: ams at gnu dot org, sgk at troutmask dot apl dot washington dot edu, wt at atmos dot colostate dot edu, fortran at gcc dot gnu dot org
Date: Thu, 02 Nov 2006 16:03:06 +0100
Subject: Re: gfortran error format (was: Re: Emacs and GFortran)
References: <19c433eb0611020608v3695ef7ex7cbe998347760d19@mail.gmail.com> <20061102142023.0BBF044043@Psilocybe.Update.UU.SE> <19c433eb0611020644x68b6191dq8fa074ed94a520aa@mail.gmail.com>

François-Xavier,


The only excuse you'll be hearing is: low-priority. Which is,
unfortunately, true. I wish we had nothing higher-profile than
diagnostic bugs for which a workaround is trivial.

Well said! Let's get gfortran giving good code for valid fortran 95, comprehensible errors in any format on invalid code and no more ICEs :-)

Paul

References:
- gfortran error format (was: Re: Emacs and GFortran)
  - From: François-Xavier Coudert
- Re: gfortran error format (was: Re: Emacs and GFortran)
  - From: Alfred M. Szmidt
- Re: gfortran error format (was: Re: Emacs and GFortran)
  - From: François-Xavier Coudert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]