/usr/share/gtk-doc/html/gmime-2.6/gmime-changes-2-0.html is in libgmime-2.6-doc 2.6.20-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>GMime 2.6 Reference Manual: Changes from 1.0 to 2.0</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="index.html" title="GMime 2.6 Reference Manual">
<link rel="up" href="gmime.html" title="Part I. GMime Overview">
<link rel="prev" href="gmime-compiling.html" title="Compiling GMime Applications">
<link rel="next" href="gmime-changes-2-2.html" title="Changes from 2.0 to 2.2">
<meta name="generator" content="GTK-Doc V1.20 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="10"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><a accesskey="u" href="gmime.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
<td><a accesskey="p" href="gmime-compiling.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="gmime-changes-2-2.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="gmime-changes-2-0"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle">Changes from 1.0 to 2.0</span></h2>
<p>Changes from 1.0 to 2.0 —
Incompatible changes made between version 1.0 and version 2.0
</p>
</td>
<td class="gallery_image" valign="top" align="right"></td>
</tr></table></div>
<div class="refsect1">
<a name="id-1.2.5.3"></a><h2>Incompatible changes from 1.0 to 2.0</h2>
<p>
See also the PORTING document in the toplevel GMime source directory.
</p>
<p>
The major change here is that I've dropped my own base object class
and have replaced it with GObject from glib-2.0. This should be a
pleasant change since you (the developer) will now be able to do many
more things such as setting arbitrary data on all GMime objects. For
additional information about GObject, please see the GObject Reference
Manual at http://developer.gnome.org/doc/API/2.0/gobject/
</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>
The first thing you need to know is that any function returning a
non-const pointer to any object /must/ be unref'd when you are done
with it. Since all objects in GMime now subclass GObject, you may
safely use <code class="function">g_object_unref()</code>
(<span class="structname">GMimeStream</span>'s may also be unref'd using
<code class="function">g_mime_stream_unref()</code>, but either way is fine).
Don't forget that
<code class="function">g_mime_part_get_content_object()</code> returns a
ref-counted <span class="structname">GMimeDataWrapper</span> object now, and
so you /must/ unref it when you have finished using it. You must also
remember to unref any GMimeDataWrapper object that you /set/ on a
GMimePart using <code class="function">g_mime_part_set_content_object()</code>
as the GMimePart will now ref the content object that you set on it.
</p></li>
<li class="listitem"><p><span class="structname">GMimeMultipart</span> is a new class which is to be
used for all multipart MIME parts rather than GMimePart (as in
1.0). There are also some subclasses of GMimeMultipart for other
things.
</p></li>
<li class="listitem"><p><code class="function">g_mime_part_[g,s]et_boundary()</code> have been removed
(see above). You must now create a GMimeMultipart object and use
<code class="function">g_mime_multipart_[g,s]et_boundary()</code>.
</p></li>
<li class="listitem"><p><code class="function">g_mime_part_add_subpart()</code> has been replaced with
<code class="function">g_mime_multipart_add_part()</code>.
</p></li>
<li class="listitem"><p><code class="function">g_mime_part_foreach()</code> has been replaced with
<code class="function">g_mime_multipart_foreach()</code> and/or
<code class="function">g_mime_message_foreach_part()</code>.
</p></li>
<li class="listitem"><p><code class="function">g_mime_part_get_subpart_from_content_id()</code> has
been replaced with
<code class="function">g_mime_multipart_get_subpart_from_content_id()</code>.
</p></li>
<li class="listitem"><p>
Another new class is <span class="structname">GMimeMessagePart</span> which
is to be used for all MIME parts containing an rfc822 message. All 1.0
GMimePart's representing message/rfc822 parts (as well as message/news
parts?) need to be migrated over to be GMimeMessagePart objects.
</p></li>
<li class="listitem"><p><span class="structname">GMimeMessagePartial</span> is another class meant
for handling the message/partial MIME type. All 1.0 GMimePart's
holding data of this type should be replaced with GMimeMessagePartial
objects.
</p></li>
<li class="listitem"><p><code class="function">g_mime_message_write_to_stream()</code> and
<code class="function">g_mime_part_write_to_stream()</code> functions have been
consolidated into a virtual method. Replace calls to these functions
with <code class="function">g_mime_object_write_to_stream()</code>. Note: while
<code class="function">g_mime_part_write_to_stream()</code> and
<code class="function">g_mime_message_write_to_stream()</code> still exist, it
is suggested you migrate to
<code class="function">g_mime_object_write_to_stream()</code>. Same goes for
<code class="function">g_mime_part_to_string()</code> and
<code class="function">g_mime_message_to_string()</code>.
</p></li>
<li class="listitem"><p><span class="structname">GMimeMessage</span>'s structure has changed a
bit. You will not be able to do <code class="literal">message->header</code>,
instead you want to do <code class="literal">((GMimeObject *)
message)->header</code>.
</p></li>
<li class="listitem"><p><code class="function">g_mime_message_set_message_id()</code> now takes a
message_id argument without the encapsulating < and >'s (it now
just takes the addr-spec portion of the msg-id).
</p></li>
<li class="listitem"><p><span class="structname">GMimeFilterFrom</span> has changed slightly, you
will want to replace all calls to
<code class="function">g_mime_filter_from_new()</code> with
<code class="function">g_mime_filter_from_new
(GMIME_FILTER_FROM_MODE_DEFAULT)</code>
(<code class="literal">GMIME_FILTER_FROM_MODE_DEFAULT</code> is equivalent to (<span class="type">int</span>) 0).
</p></li>
<li class="listitem"><p><span class="structname">GMimeParser</span> is a brand new class and
<code class="filename">gmime-parser.h</code> has had a number of API additions.
<code class="function">g_mime_parser_construct_part()</code> and
<code class="function">g_mime_parser_construct_message()</code> still exist,
however they no longer take a GMimeStream argument. Instead, they take
a GMimeParser object.
</p></li>
</ul></div>
</div>
</div>
<div class="footer">
<hr>
Generated by GTK-Doc V1.20</div>
</body>
</html>
|