[cairo] cairo 1.5.8 API Changes and bindings

[Behdad Esfahbod]

On Thu, 2008-01-31 at 10:15 -0500, Jonathon Jongsma wrote:
> On 1/30/08, Behdad Esfahbod <behdad at behdad.org> wrote:
> > Calling get_current_point() without a current point is a real error.
> > Though I can see that then it would be useful to have a separate
> > has_current_point().  If going the has_current_point() way, we may even
> > to move get_current_point() return type back to void but make it put cr
> > into error status?  That would break Pango but I don't mind much.  I can
> > fix that.
> 
> Well, from a bindings point of view, putting the cr into error status
> would present the same issue.  If bindings were following the
> recommended guidelines about checking error status after every call
> and throwing an exception if the object is in error status, this
> function would now throw an exception where it didn't previously.

Right.  We decided to back out the change and add has_current_point().
Alp wrote a patch and this will be merged soon.


-- 
behdad
http://behdad.org/

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