[cairo-bugs] [Bug 20183] New: There are misprints in the spec for " Creating paths and manipulating path data" group

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 18 01:52:47 PST 2009


http://bugs.freedesktop.org/show_bug.cgi?id=20183

           Summary: There are misprints in the spec for "Creating paths and
                    manipulating path data" group
           Product: cairo
           Version: 1.8.6
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: cworth at cworth.org
        ReportedBy: tructv at necsv.com
         QAContact: cairo-bugs at cairographics.org


- In the spec for cairo_get_current_point(), there is a reference to the
function cairo_stroke_to_path() but there isn't any specification for it in the
standard and there isn't any declaration or implementation for it in the Cairo
library source code.

So, according to us, this reference should be removed.

- In the spec for cairo_copy_path(), the standard states:
"This function will always return a valid pointer, but the result will have no
data (data==NULL and num_data==0), if either of the following conditions hold: 
1.If there is insufficient memory to copy the path. In this case path->status
will be set to CAIRO_STATUS_NO_MEMORY. 
2.If cr is already in an error state. In this case path->status will contain
the same status that would be returned by cairo_status(). 

In either case, path->status will be set to CAIRO_STATUS_NO_MEMORY (regardless
of what the error status in cr might have been)."

The sentence "In either case, path->status will be set to
CAIRO_STATUS_NO_MEMORY (regardless of what the error status in cr might have
been)" looks like redundant and opposite meaning with other parts of spec. This
sentence should be removed.

Please give us your decision.

Thank you very much for your time.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the cairo-bugs mailing list