[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs and GFortran
From: |
Alfred M. Szmidt |
Subject: |
Re: Emacs and GFortran |
Date: |
Wed, 1 Nov 2006 21:39:31 +0100 (CET) |
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.
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. It is a
simple fix, why can it simply not be applied?
Index: error.c
===================================================================
--- error.c (revision 117956)
+++ error.c (working copy)
@@ -134,6 +134,15 @@
lb = loc->lb;
f = lb->file;
+ /* Allow programs that parse GNU style error message catch the
+ error. */
+ error_printf ("%s:%d:\n", f->filename,
+#ifdef USE_MAPPED_LOCATION
+ LOCATION_LINE (lb->location)
+#else
+ lb->linenum
+#endif
+ );
error_printf ("In file %s:%d\n", f->filename,
#ifdef USE_MAPPED_LOCATION
LOCATION_LINE (lb->location)
- 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 <=
- 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, 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