public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: jruth@lci.kent.edu (Jon Ruth)
To: help-gcc@gnu.org
Subject: date_and_time in g77
Date: Mon, 13 Dec 1999 16:15:00 -0000	[thread overview]
Message-ID: <38556cab.13773883@localhost> (raw)

I'm new to gcc/g77 and would appreciate recommendations on the
following problem.

The documentation for g77 f90 intrinsic date_and_time indicates that
four parameters are returned:

	CALL Date_and_Time(Date, Time, Zone, Values)
	Date: CHARACTER; scalar; INTENT(OUT). 
	Time: CHARACTER; OPTIONAL; scalar; INTENT(OUT). 
	Zone: CHARACTER; OPTIONAL; scalar; INTENT(OUT). 
	Values: INTEGER(KIND=1); OPTIONAL; DIMENSION(8); INTENT(OUT). 

I wrote the following:

     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 (^)

I eventually reduced the call to:

     character*8 date
     call date_and_time(date)

and the compiler was happy.

I'm porting an F77 application that compiled with Watcom but used time
and date calls that g77 does not support.  The integer representations
that the array ivalues(8) should return would involve the least amount
of rewriting.

What do I need to do in order to get date_and_time to behave as
advertised?  I suspect that the proper libraries have not been
included.

    (NOTE:  We're running Debian Linux with gcc 2.95.2.  ["g77 version
     2.95.2 19991109 (Debian GNU/Linux) (from FSF-g77 version 0.5.25
     1999 1030 (prerelease))"])

Thanks.
--
Jon Ruth
Liquid Crystal Institute
Kent State University
Kent, OH

WARNING: multiple messages have this Message-ID
From: jruth@lci.kent.edu (Jon Ruth)
To: help-gcc@gnu.org
Subject: date_and_time in g77
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <38556cab.13773883@localhost> (raw)
Message-ID: <19991231222400._r5ucJEfXjASz09kvokFp_N9YsLPs-kww_hMMpYzgl8@z> (raw)

I'm new to gcc/g77 and would appreciate recommendations on the
following problem.

The documentation for g77 f90 intrinsic date_and_time indicates that
four parameters are returned:

	CALL Date_and_Time(Date, Time, Zone, Values)
	Date: CHARACTER; scalar; INTENT(OUT). 
	Time: CHARACTER; OPTIONAL; scalar; INTENT(OUT). 
	Zone: CHARACTER; OPTIONAL; scalar; INTENT(OUT). 
	Values: INTEGER(KIND=1); OPTIONAL; DIMENSION(8); INTENT(OUT). 

I wrote the following:

     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 (^)

I eventually reduced the call to:

     character*8 date
     call date_and_time(date)

and the compiler was happy.

I'm porting an F77 application that compiled with Watcom but used time
and date calls that g77 does not support.  The integer representations
that the array ivalues(8) should return would involve the least amount
of rewriting.

What do I need to do in order to get date_and_time to behave as
advertised?  I suspect that the proper libraries have not been
included.

    (NOTE:  We're running Debian Linux with gcc 2.95.2.  ["g77 version
     2.95.2 19991109 (Debian GNU/Linux) (from FSF-g77 version 0.5.25
     1999 1030 (prerelease))"])

Thanks.
--
Jon Ruth
Liquid Crystal Institute
Kent State University
Kent, OH

             reply	other threads:[~1999-12-13 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-13 16:15 Jon Ruth [this message]
1999-12-13 16:26 ` Richard Maine
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=38556cab.13773883@localhost \
    --to=jruth@lci.kent.edu \
    --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).