<div dir="ltr">Hi Tim,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 2, 2014 at 10:38 AM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">At least part the problem is that the fopen/fread etc API is dangerous unless well implemented at the lowest level. Intermixed uses of fpos and fread can easily mangle your data unless the lower level code really carefully tracks things. Our API providing fpos at the image level is decidedly dangerous, adding a second layer of possible problems.<br>
</blockquote><div><br></div><div>forgive me, but this strikes me as FUD. We're talking about adding a read-only copy, not mixing many writable files. I can't see that the API presents any hazard to the proposed usage.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
/tim<br>
{insert witticism here}<br>
<br>
><br>
><br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>