<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Patch] Skip XRef gaps in PDFDoc save methods" href="https://bugs.freedesktop.org/show_bug.cgi?id=107057#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Patch] Skip XRef gaps in PDFDoc save methods" href="https://bugs.freedesktop.org/show_bug.cgi?id=107057">bug 107057</a> from <a class="email" href="mailto:haxtibal@posteo.de" title="Tobias Deiminger <haxtibal@posteo.de>"> Tobias Deiminger</a> <pre>(In reply to oliver.sander from <a href="show_bug.cgi?id=107057#c5">comment #5</a>) > I trust your judgement on the efficiency impact. > > >Ah, and by the way, it's not to make the loop "look pretty". It's to make the > > loop non-contiguous (like 1, 4, 5, 6, 18, 19, 20,...), which is essentially the > > reason why the patch fixes the bug. > > I know that. :-) But you could have written something like Yeah, was quite sure that you knew :) And thanks for the review at all. > for(int i=0; i<xref->getNumObjects(); i++) { > if (entries[i].type == xrefEntryNone) > continue; > > which does the same, but is not as pretty. Nope, XRef::entries is private, so no access from PDFDoc. And private is a good thing, we shouldn't expose implementation details outside of XRef. An input iterator could do what you suggested while maintaining proper design. But it's not that easy to write one. If there are votes to do it, I'll try.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>