ruby-****@sourc*****
ruby-****@sourc*****
2009年 2月 1日 (日) 06:52:31 JST
-------------------------
REMOTE_ADDR = 74.15.84.244
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-glib
-------------------------
@@ -1,7 +1,7 @@
= GLib
{{link "tut-gtk2-dialog-tyu", "tut-gtk2-glib", "tut-gtk", nil}}
-On the surface ((<GLib>)) in Ruby looks a bit different from what you'd find in traditional lower level "C" implementation of GLib. The reason for this is the fact, that Ruby already utilizes some of the functionality of GLib available on that lower C level. A typical examples of these from Ryby implementation of GLib "missing" features are for instance "Memory Management" methods, "Error/Message Logging" methods, and most of the file/directory handling methods. All these facilities in fact are implemented in Ruby itself, therefore nothing is really is missing.
+On the surface ((<GLib>)) in Ruby looks a bit different from what you'd find in traditional lower level "C" implementation of GLib. The reason for this is the fact, that Ruby already utilizes some of the functionality of GLib available on that lower C level. Some typical examples of these from Ryby implementation of GLib "missing" features are for instance "Memory Management" methods, "Error/Message Logging" methods, and most of the file/directory handling methods. All these facilities in fact are implemented in Ruby itself, therefore nothing is really is missing.
Indeed you may have noticed that some features are not yet fully documented, but let that not scare you away, because as we will see they are rarely if ever needed on the level we are dealing with in this tutorial. Such for instance such is already mentioned "Error/Message" logging, for which you will find a number of ((*fixme*)) items in GLib::Log file. In Ruby most of this stuff is really rather exotic. If you need those features you are most likely not reading this tutorial, and you should get sufficient number of clues and cross references from the standard "C" GLib API documentation. In Ruby error handling with Exceptions is far superior to that implemented in standard "C" GLib API. Nevertheless, for those that deal with Exception#code and Exception#domain there are some features that could potentially improve your control, if you knew how to utilize GLib::Log paraphernalia.