unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
Cc: sgk@troutmask.apl.washington.edu, wt@atmos.colostate.edu,
		fortran@gcc.gnu.org, emacs-devel@gnu.org
Subject: Re: gfortran error format (was: Re: Emacs and GFortran)
Date: Thu,  2 Nov 2006 15:20:23 +0100 (CET)	[thread overview]
Message-ID: <20061102142023.0BBF044043@Psilocybe.Update.UU.SE> (raw)
In-Reply-To: <19c433eb0611020608v3695ef7ex7cbe998347760d19@mail.gmail.com> 	(fxcoudert@gmail.com)

   If someone wants to propose a complete patch (against subversion
   mainline) that works, regression-tests fine, please send it and it
   will be reviewed like any other patch.

A purposed patch that makes gfortran follow the GCS is already
purposed and submitted, two version of it one backward compatible (g77
style) and one that is not exist.  It has been repeated a billion
times that gfortran does not have to follow the GCS to the letter,
only allow to jump to the error location.  If you or anyone else
wishes to do that, please do, but this is not what was requested.

   PS: One thing that I would like to note, however: changing the
   format of error messages is not something we can do out of the
   blue. Some tools already handle the gfortran error messages, so we
   probably don't want to make life too hard for them.

I already purposed a backward compatible version of the format that
should work with tools that parse the "old" format, this is what g77
did for example; this fact has also been repeated several times now.


I do not wish to spend any more on this, so this will be my last
message on the topic, I think it is clear what should be done, and
what is requested is a trivial change but people being stubborn and
making up excuses.


  reply	other threads:[~2006-11-02 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 14:08 gfortran error format (was: Re: Emacs and GFortran) François-Xavier Coudert
2006-11-02 14:20 ` Alfred M. Szmidt [this message]
2006-11-02 15:40   ` Steve Kargl
2006-11-02 20:14 ` gfortran error format David Kastrup
2006-11-03  7:08 ` gfortran error format (was: Re: Emacs and GFortran) Richard Stallman
2006-11-03  7:54   ` Erik Edelmann
2006-11-03  9:06     ` François-Xavier Coudert
2006-11-04  6:38     ` Richard Stallman
2006-11-03  8:21   ` Brooks Moses
2006-11-03 14:14     ` gfortran error format Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061102142023.0BBF044043@Psilocybe.Update.UU.SE \
    --to=ams@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fortran@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    --cc=wt@atmos.colostate.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).