<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Fix warning on deprecated Poppler::Annotation::window" href="https://bugs.freedesktop.org/show_bug.cgi?id=57807#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Fix warning on deprecated Poppler::Annotation::window" href="https://bugs.freedesktop.org/show_bug.cgi?id=57807">bug 57807</a> from <a class="email" href="mailto:adamreichold@myopera.com" title="Adam Reichold <adamreichold@myopera.com>"> Adam Reichold</a> <pre>Created <a href="attachment.cgi?id=71211" name="attach_71211" title="Locally disable deprecation warnings">attachment 71211</a> <a href="attachment.cgi?id=71211&action=edit" title="Locally disable deprecation warnings">[details]</a> <a href='page.cgi?id=splinter.html&bug=57807&attachment=71211'>[review]</a> Locally disable deprecation warnings Hello, Personally, I think those warnings are rather helpful since they remind us that this deprecated member should go away at some point in time. (Even though I don't know how deprecation periods are currently handled in Poppler.) Besides that, I think you really want to temporarily and locally disable the warning and not the deprecation itself. If one really wants to do this and still tackle several compilers, maybe something like the attached patch could be used. But still, I think the warning should stay with a long-term plan on removing the offender, i.e. the declaration itself. Regards, Adam.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>