[cairo-bugs] [Bug 20132] New: The behavior of cairo_status_to_string() function is inconsistency with the spec

[bugzilla-daemon at freedesktop.org]

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

           Summary: The behavior of cairo_status_to_string() function is
                    inconsistency with the spec
           Product: cairo
           Version: 1.8.6
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: medium
         Component: general
        AssignedTo: cworth at cworth.org
        ReportedBy: tructv at necsv.com
         QAContact: cairo-bugs at cairographics.org


Created an attachment (id=22973)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22973)
The C test program to demonstrate this issue

The cairo-1.8.6 API reference states that cairo_status_to_string() function
returns a string representation of the status. So when this function is called
with status such as “CAIRO_STATUS_SUCCESS”, it should return “return no
error has occurred” instead of “success”.

The following statuses have the similar inconsistency cases:
CAIRO_STATUS_SUCCESS 
CAIRO_STATUS_INVALID_RESTORE 
CAIRO_STATUS_INVALID_POP_GROUP 
CAIRO_STATUS_SURFACE_FINISHED 
CAIRO_STATUS_INVALID_DSC_COMMENT 
CAIRO_STATUS_INVALID_INDEX 
CAIRO_STATUS_CLIP_NOT_REPRESENTABLE 
CAIRO_STATUS_TEMP_FILE_ERROR 
CAIRO_STATUS_INVALID_STRIDE 
CAIRO_STATUS_FONT_TYPE_MISMATCH 
CAIRO_STATUS_USER_FONT_IMMUTABLE 
CAIRO_STATUS_USER_FONT_ERROR 
CAIRO_STATUS_NEGATIVE_COUNT 
CAIRO_STATUS_INVALID_CLUSTERS 
CAIRO_STATUS_INVALID_SLANT 
CAIRO_STATUS_INVALID_WEIGHT 

Although these found inconsistences do no harm. But according to us, they
should be fixed to gain more end user's confidence.

Included with this report is the C test program to demonstrate this issue.

Please, give us your decision.

Thank you 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.