search for: 75yw9bf3

...ith static linking, so no external > dependencies hinder its function. > > If you take a look at the following MSDN pages for Visual Studio 2005, you > will see that _fseeki64 and _ftelli64 are supported all the way back to > Windows 95: > http://msdn.microsoft.com/en-**us/library/75yw9bf3%28v=vs.80%**29.aspx<http://msdn.microsoft.com/en-us/library/75yw9bf3%28v=vs.80%29.aspx>and > http://msdn.microsoft.com/en-**US/library/0ys3hc0b%28v=vs.80%**29.aspx<http://msdn.microsoft.com/en-US/library/0ys3hc0b%28v=vs.80%29.aspx> > > > > > > ---------- Forwarded m...

On 5.5.2013 18:02, Timothy B. Terriberry wrote: > > Instead I've attached a patch that uses fgetpos/fsetpos. This is > totally untested (I haven't even checked it compiles), but the idea > should work. > You people do realize these hacks would only be required for 10+ year old obsolete compilers?

...hat this happens with text files because Windows inserts extra characters at end-of-lines when reading "text" mode files (but with binary files, things should be fine.) This particular issue is documented in Microsoft Windows documentation (e.g., at http://msdn2.microsoft.com/library/75yw9bf3(en-us,vs.80).aspx, found by searching on Google using the terms "fseek windows documentation"). Are there any known issues using seek with binary files under Windows? If there are not, then the caveat could be made specific to text files and all vagueness removed. -- Tony Plate >...

...configured to be compiled with static linking, so no external dependencies hinder its function. If you take a look at the following MSDN pages for Visual Studio 2005, you will see that _fseeki64 and _ftelli64 are supported all the way back to Windows 95: http://msdn.microsoft.com/en-us/library/75yw9bf3%28v=vs.80%29.aspx and http://msdn.microsoft.com/en-US/library/0ys3hc0b%28v=vs.80%29.aspx

..., so no > external dependencies hinder its function. > > If you take a look at the following MSDN pages for Visual Studio > 2005, you will see that _fseeki64 and _ftelli64 are supported all > the way back to Windows 95: > http://msdn.microsoft.com/en-us/library/75yw9bf3%28v=vs.80%29.aspx and > http://msdn.microsoft.com/en-US/library/0ys3hc0b%28v=vs.80%29.aspx > > > > > > ---------- Forwarded message ---------- > From: Ralph Giles <giles at thaumas.net <mailto:giles at thaumas.net>> > To: flac-dev at xiph.org &...

...h text files > because Windows inserts extra characters at end-of-lines when reading > "text" mode files (but with binary files, things should be fine.) This > particular issue is documented in Microsoft Windows documentation (e.g., > at http://msdn2.microsoft.com/library/75yw9bf3(en-us,vs.80).aspx, found > by searching on Google using the terms "fseek windows documentation"). > Are there any known issues using seek with binary files under Windows? > If there are not, then the caveat could be made specific to text files > and all vagueness removed....