[cairo] Call for testers: Const status accessors

[M Joonas Pihlaja]

On Fri, 5 Aug 2011, Andrea Canciani wrote:

> An alternative patch (which I would prefer, if it didn't possibly cause
> new warnings in existing software) would just remove const from
> cairo_region_status().
>
> Would such a patch be preferred?

I prefer no patch at all since the region API is internally consistent
with respect to const tagging, and we already have a mixed bag of
const qualified/unqualified types.... font options being a precedent
here.  IMO internal API consistency within a type takes precedence
over consistency across types if we can't have both.

Joonas