New muPDF compiler warnings - 2017-10-25-13:00:02 - abd4c0da5d50cc5b81e430dea3eaa01502370dad

Previous Revision: a1e696d27e0927855dd2e0d505afd571b0f37ed7
 Current Revision: abd4c0da5d50cc5b81e430dea3eaa01502370dad

commit abd4c0da5d50cc5b81e430dea3eaa01502370dad
Author:     Robin Watts <[email protected]>
AuthorDate: Thu Sep 21 14:10:33 2017 +0100
CommitDate: Tue Oct 24 15:16:36 2017 +0100

    Improved overprint (simulation) control.
    
    First, we add an fz_page_overprint function to detect if a
    page uses overprint. Only PDF implements this currently (other
    formats all return false). PDF looks for '/OP true' in any
    ExtGState entry.
    
    We make Mutool check this. If it finds it, and spot rendering
    is not completely disabled, then it ensures that the separation
    object passed to the pixmap into which we draw is non NULL. This
    causes the draw device to do overprint simulation.
    
    We ensure that mutool draw defaults to having the spot rendering
    mode default to simulation in builds that support it.
    
    Finally, we ensure that if an output intent is set by the document,
    and spot rendering is not completely disabled, then we ensure the
    seps object is non NULL so that we render to a group in the
    specified output intent, and THEN convert down to the required
    colorspace for the output.
    
    This should make us match acrobats behaviour.

include/mupdf/fitz/document.h
include/mupdf/pdf/object.h
include/mupdf/pdf/page.h
source/fitz/document.c
source/pdf/pdf-object.c
source/pdf/pdf-page.c
source/tools/mudraw.c



muPDF:

new cppcheck warnings (Cppcheck 1.72): 

source/tools/mudraw.c:1257: error: Memory leak: p

http://miles.ghostscript.com:8080/artifex/mupdf/abd4c0da5d50cc5b81e430dea3eaa01502370dad/mupdf-cppcheck.txt