unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Fran?ois-Xavier Coudert <fxcoudert@gmail.com>,
	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 07:40:11 -0800	[thread overview]
Message-ID: <20061102154011.GA45031@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20061102142023.0BBF044043@Psilocybe.Update.UU.SE>

On Thu, Nov 02, 2006 at 03:20:23PM +0100, Alfred M. Szmidt wrote:
> 
> 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.
> 

I already showed you that those two purposed and submitted
patches cause over 2000 regression in the gfortran testsuite.

-- 
Steve


  reply	other threads:[~2006-11-02 15:40 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
2006-11-02 15:40   ` Steve Kargl [this message]
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=20061102154011.GA45031@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=emacs-devel@gnu.org \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --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).