Looks like the culprit is the condition to escape the repeat structure. The result never reach the EOF "end of file".
Which other condition could i use to verify that the file have been reading completely? Thanks in advance! Al > In this enhancement request written by Mark Schonewille: > http://quality.runrev.com/qacenter/show_bug.cgi?id=2410 > > Mark Waddingham posted this function: > > function quasiMD5 pFile > local tMD5s > open file pFile for binary read > repeat > read from file pFile for 4096 chars > if the result is EOF then -- Alert!!! the result never reach "EOF" > exit repeat > end if > put the md5digest of it after tMD5s > end repeat > close file pFile > return the md5Digest of tMD5s > end quasiMD5 > > But when i run this function, Rev > consumes all memory available. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/MD5-digests-of-very-big-files-tp2270182p2270228.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
