[cairo] RFC: converting public API to use const

Behdad Esfahbod behdad at behdad.org
Tue May 8 15:19:03 PDT 2007

On Tue, 2007-05-08 at 17:30 -0400, Chris Wilson wrote:
> Recently I've had the unpleasant task of having to cast calls to
> cairo_font_option_status() in order to avoid the compiler warnings when
> trying to call the function with a const cairo_font_options_t.
> Does anyone have any objects to changing:
>     cairo_status_t cairo_font_options_status (cairo_font_options_t *);
> to
>     cairo_status_t cairo_font_options_status (const cairo_font_options_t *);
> i.e. can anyone identify a situation where this change will break the
> ABI or feels it is an incompatible change in the API?
> --
> Chris Wilson

AFAIR we have made such changes before.  Fine with me.


"Those who would give up Essential Liberty to purchase a little
 Temporary Safety, deserve neither Liberty nor Safety."
        -- Benjamin Franklin, 1759

More information about the cairo mailing list