public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40377]  New: gfortran documentation: Add note to C prog. part + update F200x status
Date: Mon, 08 Jun 2009 07:03:00 -0000	[thread overview]
Message-ID: <bug-40377-13404@http.gcc.gnu.org/bugzilla/> (raw)

The GNU Fortran manual should mention in the mixed-language programming section
that
  C's  A[i][j]
matches
  Fortran's A(j,i)
and that A(j+1,i) follows A(j,i) in memory.

Cf. http://gcc.gnu.org/onlinedocs/gfortran/Mixed_002dLanguage-Programming.html

 * * *

The Fortran 2003/2009 status should be updated based on:
http://gcc.gnu.org/wiki/Fortran2003
http://gcc.gnu.org/wiki/Fortran2003Status
http://gcc.gnu.org/wiki/Fortran2008Status
http://gcc.gnu.org/wiki/GFortran#news
Release notes, e.g.,
http://gcc.gnu.org/gcc-4.4/changes.html

cf. http://gcc.gnu.org/onlinedocs/gfortran/Fortran-2003-and-2008-status.html


-- 
           Summary: gfortran documentation: Add note to C prog. part +
                    update F200x status
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40377


             reply	other threads:[~2009-06-08  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:03 burnus at gcc dot gnu dot org [this message]
2009-06-08 19:03 ` [Bug fortran/40377] " burnus at gcc dot gnu dot org
2009-06-13 19:21 ` pinskia at gcc dot gnu dot org
2009-12-07 15:35 ` burnus at gcc dot gnu dot org
2009-12-08  8:52 ` burnus at gcc dot gnu dot org
2009-12-08  8:53 ` burnus at gcc dot gnu dot org

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

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

  git send-email \
    --in-reply-to=bug-40377-13404@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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. 
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).