comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: big file navigation
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: big file navigation [message #36780 is a reply to message #36777] Tue, 28 October 2003 11:53 Go to previous messageGo to previous message
R.G. Stockwell is currently offline  R.G. Stockwell
Messages: 363
Registered: July 1999
Senior Member
"Ben Tupper" <btupper@bigelow.org> wrote in message
news:bnm487$1317fk$1@ID-189398.news.uni-berlin.de...
...
> IDL> for i = 0L, 55855-1 do readU, U,d
>
>
> Problem solved! I can break the file into smaller 'chunks' of 4GB by
reading in
> images and writing them to a new file. OK!
>
> But here's what I wish I understood (and could exploit!) Somewhere the
system is
> keeping track of the file location so that READU knows where to read. So,
deep
> down in its guts, IDL is navigating its way through with 64-bit file
offsets.
> Ain't it? Is there anything here I could get my hooks into so I don't
have to
> break the original file into smaller ones?
>
> Cheers,
> Ben

The point_lun seems to use a 64 bit offset

from the help:

If Unit is negative, Position must be a named variable into which the
current file position will be stored. The returned type will be a longword
signed integer if the position is small enough to fit, and an unsigned
64-bit integer otherwise.


Cheers,
bob
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Trouble wih events
Next Topic: about contour

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:29:21 PDT 2025

Total time taken to generate the page: 0.00409 seconds