[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs and GFortran
From: |
Eli Zaretskii |
Subject: |
Re: Emacs and GFortran |
Date: |
Wed, 01 Nov 2006 01:01:23 +0200 |
> Date: Tue, 31 Oct 2006 07:10:22 -0800
> From: Steve Kargl <address@hidden>
> Cc: address@hidden, address@hidden
>
> laptop:kargl[219] gfc -c l.f90
> In file l.inc:1
>
> Included at l.f90:2
>
> integer i
> 1
> In file l.f90:3
>
> call i(j)
> 2
> Error: 'i' at (1) has a type, which is not consistent with the CALL at (2)
GCC outputs similar error messages without any difficulty, and without
violating the GNU standard:
In file included from foo.h:79:,
from bar.c:20:
baz.h:34:10: error: conflicting types for 'whatever'
another.h:63:7: error: previous declaration of 'whatever' was here
(It doesn't show the actual offending line(s), but adding that would
not interfere with parsing the messages.)
> Is "NO" some difficult concept for you to understand?
Ah, the winning argument...
- Re: Emacs and GFortran, (continued)
- Re: Emacs and GFortran, Stefan Monnier, 2006/10/31
- Re: Emacs and GFortran, FX Coudert, 2006/10/31
- Re: Emacs and GFortran, Richard Stallman, 2006/10/31
- Re: Emacs and GFortran, Miles Bader, 2006/10/31
- Re: Emacs and GFortran, Angelo Graziosi, 2006/10/31
- Re: Emacs and GFortran, Steve Kargl, 2006/10/31
- Re: Emacs and GFortran, Angelo Graziosi, 2006/10/31
- Re: Emacs and GFortran, Chong Yidong, 2006/10/31
- Re: Emacs and GFortran,
Eli Zaretskii <=
Re: Emacs and GFortran, François-Xavier Coudert, 2006/10/30