search for: 70hdhh4t

...pos. This is totally >> untested (I haven't even checked it compiles), but the idea should work. >> > MSDN says "The pos value is stored in an internal format and is intended > for use only by *fgetpos* and *fsetpos*." (http://msdn.microsoft.com/en-** > us/library/70hdhh4t%28v=vs.80%**29.aspx<http://msdn.microsoft.com/en-us/library/70hdhh4t%28v=vs.80%29.aspx>), > so I don't think it's a good idea to use it this way even if tests > suggested it works. > > I'll write a test program tomorrow to try the fflush+_lseeki64 approach. > > A...

...that uses fgetpos/fsetpos. This is > totally untested (I haven't even checked it compiles), but the idea > should work. MSDN says "The pos value is stored in an internal format and is intended for use only by *fgetpos* and *fsetpos*." (http://msdn.microsoft.com/en-us/library/70hdhh4t%28v=vs.80%29.aspx), so I don't think it's a good idea to use it this way even if tests suggested it works. I'll write a test program tomorrow to try the fflush+_lseeki64 approach. Another solution - although a bit ugly - might be to disable buffering on Windows using setvbuf.

...is totally untested (I haven't even checked it compiles), but > the idea should work. > > MSDN says "The pos value is stored in an internal format and is > intended for use only by *fgetpos* and *fsetpos*." > (http://msdn.microsoft.com/en-us/library/70hdhh4t%28v=vs.80%29.aspx), > so I don't think it's a good idea to use it this way even if tests > suggested it works. > > I'll write a test program tomorrow to try the fflush+_lseeki64 > approach. > > Another solution - although a bit ugly - might be to...

On 5/5/2013 09:03, Timothy B. Terriberry wrote: > Robert Kausch wrote: >> The _lseeki64 patch probably is a little more controversial. The problem >> is that fseeki64 and ftelli64 are not available in Windows XP - at least >> not without installing extra MSVC runtime libraries. I changed compat.h >> and replaced them with calls to _lseeki64, which was available at least