Well, I don't really know for sure. All I know is that the standard C API for file I/O does weird things on 32-bit Windows and Linux with files >= 2 GB, and takes ints in places where a properly designed API would take something wider. Phobos merely propagates the defects of the underlying C API.<br>
<br><div class="gmail_quote">On Mon, Aug 16, 2010 at 1:05 PM, Andrei Alexandrescu <span dir="ltr"><<a href="mailto:andrei@erdani.com">andrei@erdani.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">David Simcha wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
...not to mention that on 32-bit standard C FILE*s are 32-bit and do weird things when you get over the 2GB mark. IMHO this is by far the biggest problem with them.<br>
</blockquote>
<br></div>
I don't understand this. So are you saying that the FILE pointer itself has issues?<br>
<br>
By and large, I dislike playing nice with FILE* as much as the next guy but I've looked into this many times and couldn't find a way to either play nice with C libraries, or downgrading the importance of doing so.<br>
<font color="#888888">
<br>
<br>
Andrei</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
phobos mailing list<br>
<a href="mailto:phobos@puremagic.com" target="_blank">phobos@puremagic.com</a><br>
<a href="http://lists.puremagic.com/mailman/listinfo/phobos" target="_blank">http://lists.puremagic.com/mailman/listinfo/phobos</a><br>
</div></div></blockquote></div><br>