From: Richard Maine <maine@altair.dfrc.nasa.gov>
To: help-gcc@gnu.org
Subject: Re: date_and_time in g77
Date: Mon, 13 Dec 1999 16:26:00 -0000 [thread overview]
Message-ID: <ueogbutme7.fsf@linux.dfrc.nasa.gov> (raw)
In-Reply-To: <38556cab.13773883@localhost>
jruth@lci.kent.edu (Jon Ruth) writes:
> I'm new to gcc/g77 and would appreciate recommendations on the
> following problem....
> character*10 datizn(3)
> integer*2 ivalues(8)
> call date_and_time(datizn(1),datizn(2),datizn(3),ivalues)
>
> and received the following error message:
>
> call date_and_time(datizn(1),datizn(2),datizn(3),ivalues)
> ^
> Too many arguments passed to intrinsic `DATE_AND_TIME' at (^)
Did this accidentally get reposted? I answered this (and Toon followed
up on my answer, so I know it got out) 5 days ago. See the previous
answer (which was in comp.lang.fortran only).
In short, you got the argument type for ivalues wrong. It should
be integer, not integer*2. For the longer version, see my previous
post.
--
Richard Maine
maine@altair.dfrc.nasa.gov
WARNING: multiple messages have this Message-ID
From: Richard Maine <maine@altair.dfrc.nasa.gov>
To: help-gcc@gnu.org
Subject: Re: date_and_time in g77
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <ueogbutme7.fsf@linux.dfrc.nasa.gov> (raw)
Message-ID: <19991231222400.1-N3Uz5IiiUVfVV5Al_uBTC324nCiOAFppfU9PEjY1E@z> (raw)
In-Reply-To: <38556cab.13773883@localhost>
jruth@lci.kent.edu (Jon Ruth) writes:
> I'm new to gcc/g77 and would appreciate recommendations on the
> following problem....
> character*10 datizn(3)
> integer*2 ivalues(8)
> call date_and_time(datizn(1),datizn(2),datizn(3),ivalues)
>
> and received the following error message:
>
> call date_and_time(datizn(1),datizn(2),datizn(3),ivalues)
> ^
> Too many arguments passed to intrinsic `DATE_AND_TIME' at (^)
Did this accidentally get reposted? I answered this (and Toon followed
up on my answer, so I know it got out) 5 days ago. See the previous
answer (which was in comp.lang.fortran only).
In short, you got the argument type for ivalues wrong. It should
be integer, not integer*2. For the longer version, see my previous
post.
--
Richard Maine
maine@altair.dfrc.nasa.gov
next prev parent reply other threads:[~1999-12-13 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-13 16:15 Jon Ruth
1999-12-13 16:26 ` Richard Maine [this message]
1999-12-31 22:24 ` Richard Maine
1999-12-31 22:24 ` Jon Ruth
-- strict thread matches above, loose matches on Subject: below --
1999-12-13 12:47 Jon Ruth
1999-12-31 22:24 ` Jon Ruth
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=ueogbutme7.fsf@linux.dfrc.nasa.gov \
--to=maine@altair.dfrc.nasa.gov \
--cc=help-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).