public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: craig@jcb-sc.com
To: RICHARD_ELMQUIST@udlp.com
Cc: craig@jcb-sc.com
Subject: Re: Having problems with DATA Statement
Date: Fri, 16 Apr 1999 08:35:00 -0000	[thread overview]
Message-ID: <19990416153328.10559.qmail@deer> (raw)
In-Reply-To: <002C49D5.C21254@udlp.com>

>I'm trying to use g77 to compile fortran code that I know works else where.  I
>get a comiler message indicating that it can't initialize the second value of FS
>in the following line,
>
>DATA (FS(1,J),J=4,200) /197*1.0/
>
>As far as I know this is a valid FORTRAN statement, and I can't find anything on
>DATA Statements in the online documentation.
>
>Can you please help me out?

Please read the documentation on submitting bug reports.

        tq vm, (burley)

WARNING: multiple messages have this Message-ID
From: craig@jcb-sc.com
To: RICHARD_ELMQUIST@udlp.com
Cc: craig@jcb-sc.com
Subject: Re: Having problems with DATA Statement
Date: Fri, 30 Apr 1999 23:15:00 -0000	[thread overview]
Message-ID: <19990416153328.10559.qmail@deer> (raw)
Message-ID: <19990430231500.oxFC7cYri5lVucNFM-oJmQ5Zooos_ak_rMTpAt92h74@z> (raw)
In-Reply-To: <002C49D5.C21254@udlp.com>

>I'm trying to use g77 to compile fortran code that I know works else where.  I
>get a comiler message indicating that it can't initialize the second value of FS
>in the following line,
>
>DATA (FS(1,J),J=4,200) /197*1.0/
>
>As far as I know this is a valid FORTRAN statement, and I can't find anything on
>DATA Statements in the online documentation.
>
>Can you please help me out?

Please read the documentation on submitting bug reports.

        tq vm, (burley)

  reply	other threads:[~1999-04-16  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-15  6:36 RICHARD_ELMQUIST
1999-04-16  8:35 ` craig [this message]
1999-04-30 23:15   ` craig
1999-04-30 23:15 ` RICHARD_ELMQUIST

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=19990416153328.10559.qmail@deer \
    --to=craig@jcb-sc.com \
    --cc=RICHARD_ELMQUIST@udlp.com \
    /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).