[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs and GFortran
From: |
Steve Kargl |
Subject: |
Re: Emacs and GFortran |
Date: |
Wed, 1 Nov 2006 13:30:56 -0800 |
User-agent: |
Mutt/1.4.2.2i |
On Wed, Nov 01, 2006 at 09:39:31PM +0100, Alfred M. Szmidt wrote:
> You will need to audit each and every one to ensure that the
> messages meet your expectations. You'll then need to fix the
> testsuite.
>
> This is not needed, you are exaggerating beyond belief Steve.
Have you actually read gfortran source code other than error.c?
> Here is another version that is should be backward compatible with the
> bits that the testsuite parses. This will fix the problem the
> original user reported; namley allowing programs that parse GNU style
> error message to jump to the location of the error/warning.
I've already posted a counter example that will not allow a
person to jump to the location of the error. You need to
read the entire error message to decide where the error is.
--
Steve
- Re: Emacs and GFortran, Richard Stallman, 2006/11/01
- Re: Emacs and GFortran, Warren Turkal, 2006/11/01
- Re: Emacs and GFortran, Steve Kargl, 2006/11/01
- Re: Emacs and GFortran, Stefan Monnier, 2006/11/01
- Re: Emacs and GFortran, Alfred M. Szmidt, 2006/11/01
- Re: Emacs and GFortran,
Steve Kargl <=
- Re: Emacs and GFortran, Alfred M. Szmidt, 2006/11/01
- Re: Emacs and GFortran, Steve Kargl, 2006/11/01
- Re: Emacs and GFortran, Alfred M. Szmidt, 2006/11/01
- Re: Emacs and GFortran, Steve Kargl, 2006/11/01
- Re: Emacs and GFortran, Alfred M. Szmidt, 2006/11/01
- Re: Emacs and GFortran, Steve Kargl, 2006/11/01
- Re: Emacs and GFortran, Chong Yidong, 2006/11/02
- Re: Emacs and GFortran, David Kastrup, 2006/11/03
- Re: Emacs and GFortran, Steve Kargl, 2006/11/03
- Re: Emacs and GFortran, Chong Yidong, 2006/11/02