home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!mcsun!sunic!kth.se!hemul.nada.kth.se!d88-jwa
- From: d88-jwa@hemul.nada.kth.se (Jon WΣtte)
- Subject: Re: Getting Size of Large Files
- Message-ID: <1992Dec29.234156.4349@kth.se>
- Sender: usenet@kth.se (Usenet)
- Nntp-Posting-Host: hemul.nada.kth.se
- Organization: Royal Institute of Technology, Stockholm, Sweden
- References: <ofDwLZCSMUI3IEX0Ef@transarc.com>
- Date: Tue, 29 Dec 1992 23:41:56 GMT
- Lines: 26
-
- In <ofDwLZCSMUI3IEX0Ef@transarc.com> Barry_Wolman@transarc.com writes:
-
- >calling PBGetEOF. I reviewed the code and checked Think Reference; I
- >can't understand why the code works for small files and fails for
-
- You called PBOpen as well. WHy not at least use PBHOpen?
- Or better yet, HOpen and GetEOF as high-level parts?
-
-
- SFGetFile...
- GetWDInfo ( reply . vRefNum , & vRefNum , & dirID , & junk ) ;
- HOpen ( vRefNum , dirID , reply . fName , fsRdPerm , & refNum ) ;
- GetEOF ( refNum , & len ) ;
-
- With error checking of course. The use FSRead; and why read LINES
- when you can read and spool BLOCKS of data? The printer doesn't
- care, and it's faster and more efficient.
-
- Cheers,
-
- / h+
-
- --
- -- Jon W{tte, h+@nada.kth.se, Mac Hacker Deluxe --
-
- -- I don't fear death, it's dying that scares me.
-