Article View: gnu.misc.discuss
Article #2269Re: Q: Fortran unformatted i/o with GNU f2c/gcc problem.
From: Raymond Toy
Date: Fri, 02 Oct 1998 00:00
Date: Fri, 02 Oct 1998 00:00
14 lines
1229 bytes
1229 bytes
>>>>> "Chris" == Chris Metzler <metzler@oddjob.uchicago.edu> writes:
Chris> Anyway, thanks for cluing me in re: unformatted file strucutre.
There is one more option, but that would probably require a fair
number of changes to you code. Use unformatted, random access files.
Most compilers that I've used support this, and they produce exactly
the data: no record separators or anything---just exactly what you
said to write.
But then all I/O has to be in records of fixed size and you may not
want this.
Ray
Technical Details
Message-ID:
<4nn27evqdk.fsf@rtp.ericsson.se>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<F02psK.Apn@midway.uchicago.edu> <lpaF02tvI.5Aw@netcom.com> <F041A8.Ix@midway.uchicago.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,e0781954572e0423 X-Google-Attributes: gid11318c,public X-Google-Thread: 1025b4,e0781954572e0423 X-Google-Attributes: gid1025b4,public From: Raymond Toy <toy@rtp.ericsson.se> Subject: Re: Q: Fortran unformatted i/o with GNU f2c/gcc problem. Date: 1998/10/02 Message-ID: <4nn27evqdk.fsf@rtp.ericsson.se> X-Deja-AN: 397101460 Sender: toy@wcsdsp4 References: <F02psK.Apn@midway.uchicago.edu> <lpaF02tvI.5Aw@netcom.com> <F041A8.Ix@midway.uchicago.edu> Content-Type: text/plain; charset=US-ASCII Organization: Ericsson Inc., RTP, NC Mime-Version: 1.0 (generated by tm-edit 7.108) Newsgroups: gnu.misc.discuss,gnu.gcc.help