Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Two VastF90 questions
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
bglbv  
View profile  
 More options Mar 23 1999, 3:00 am
Newsgroups: comp.lang.fortran
From: bg...@my-dejanews.com
Date: 1999/03/23
Subject: Re: Two VastF90 questions

berge...@iaehv.IAEhv.nl (Jos Bergervoet) writes:
> >How about READ (..., ADVANCE='NO') ? If the underlying Fortran 77

> Good point. That one isn't translated (but what would be it's use?)

How about finding out the actual size of an input record (via the
SIZE= keyword)? Or handling arbitrarily long lines of input by
looping with READ(...,ADVANCE='NO',IOSTAT=ios,SIZE=isize) until
(ios<0) ?

> >In the case of g77, perhaps it would be a good idea for someone to
> >add full ADVANCE='NO' support to libg2c (or however it's now called)
> I would very much prefer the qualified craftspersons to postpone that,
> and FIRST include allocatable arrays (pointers may be postponed also,
> of course.)

You are assuming that the qualified craftmen are the same for both
enhancements. This need not be so, as most of the work for
non-advancing I/O is in modifying the I/O library while ALLOCATABLE
support has far deeper implications for the compiler itself.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.