mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2026-05-05 15:48:00 +02:00
Merge branch 'fix-error-handling-docs' into 'master'
Docs: Remove out of date remarks See merge request cairo/cairo!450
This commit is contained in:
commit
7f334e0479
1 changed files with 0 additions and 10 deletions
|
|
@ -423,14 +423,6 @@ public void writeToPNG (OutputStream stream) throws IOException;
|
|||
operations do nothing. Retrieving the status of the
|
||||
singleton object returns <constant>CAIRO_STATUS_NO_MEMORY</constant>
|
||||
</para>
|
||||
<remark>
|
||||
Is this going to apply to
|
||||
<type>cairo_surface_t</type> as well?
|
||||
</remark>
|
||||
<remark>
|
||||
What about cairo_copy_path_data()? It's probably going to
|
||||
have to return <constant>NULL</constant>.
|
||||
</remark>
|
||||
</listitem>
|
||||
<listitem><para>
|
||||
Errors propagate from object to object. Setting a pattern
|
||||
|
|
@ -438,8 +430,6 @@ public void writeToPNG (OutputStream stream) throws IOException;
|
|||
<type>cairo_t</type> puts the type into an error state.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
<remark>Much of the above is not yet implemented at the time of
|
||||
this writing</remark>
|
||||
<para>
|
||||
A language binding could copy the C approach, and for a
|
||||
language without exceptions, this is likely the right thing
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue