On 8/9/2011 2:14 PM, Ted Roche wrote: > I think you've got a typo there. It should be: > > #DEFINE BLOW RELEASE > BLOW aChunks > > If you're processing a large file (and large keeps changing in > definition), it may make more sense to read it a line at a time, > processing each line of data as you go, rather than trying to slurp > megabytes into memory, first as an unnamed string (the return of > FILETOSTR()) and then allocating again that amount of memory as an > array. Let the OS do the buffering and not VFP. > > With buffered low-level file functions reading files on your local > discs, I'd hazard a guess you'll see no difference in processing time. > It's worth a few minutes of benchmarking to confirm, of course.
LOL! Hilarious, Ted! Yeah, I think processing LLFF is a better way to go. I'm gonna have to bone up on how those F_ commands work now. -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
