[cairo-bugs] [Bug 5676] CAIROMM: Add bindings for more surface types

[bugzilla-daemon at freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=5676          
     

murrayc at murrayc.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|CAIROMM: Add bindings for   |CAIROMM: Add bindings for
                   |more surface types          |more surface types




------- Additional Comments From murrayc at murrayc.com  2006-01-21 23:17 -------
About exceptions:
We have generally avoided this in gtkmm and libxml++ because it seems to make
life more difficult and it requires us to know about every possible exception at
the time that we stabilize the API/ABI. Sorry, but I don't remember all of the
reasoning. The best I can find at the moment is here:
http://marc.theaimsgroup.com/?l=gtkmm&m=101515928306805&w=2
So, for now, I'd like to remove the throw() specifications.

Doxygen has @throws which does the job of documenting it without making extra
demands on the programmer.

>  I removed the status check from a couple of functions that (according to
> my perusal of the cairo source code) don't seem to change the internal status
> of the cairo object.

Is there any way to be sure that these won't change something in future? I'd
like some documentation/confirmation of this from the cairo developers. So far,
Carl Worth has told us that it's probably a good idea to check the status after
every call, in languages where that is viable.

I don't think that get_user_data() should be wrapped at all. It doesn't seem
useful. I think I have documented that elsewhere. If we add it now, even
protected, we can't remove it later.

What does "XXX" mean in comments? Please be more explicit. I use TODO: for
things that need more attention.

Otherwise this is wonderful and should be committed.
          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.