Summary: |
The behavior of cairo_status_to_string() function is inconsistency with the spec |
Product: |
cairo
|
Reporter: |
Truc Truong <tructv> |
Component: |
general | Assignee: |
Carl Worth <cworth> |
Status: |
RESOLVED
WONTFIX
|
QA Contact: |
cairo-bugs mailing list <cairo-bugs> |
Severity: |
minor
|
|
|
Priority: |
medium
|
|
|
Version: |
1.8.6 | |
|
Hardware: |
All | |
|
OS: |
All | |
|
Whiteboard: |
|
i915 platform:
|
|
i915 features:
|
|
Attachments: |
The C test program to demonstrate this issue
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 22973 [details] 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.