Make EMailPartList thread-safe.

Exposing data members in the public struct is unwise, especially when
EMailPartList is used from multiple threads.  Instead keep the members
private and provide a set of thread-safe functions to manipulate them.

1 files changed, 3 insertions, 3 deletions

diff --git a/em-format/e-mail-formatter-utils.c b/em-format/e-mail-formatter-utils.c
index 7c01f323bb..11dcc0e10b 100644
--- a/em-format/e-mail-formatter-utils.c
+++ b/em-format/e-mail-formatter-utils.c
@@ -419,15 +419,15 @@ e_mail_formatter_format_header (EMailFormatter *formatter,
 	g_free (str_field);
 }
 
-GSList *
-e_mail_formatter_find_rfc822_end_iter (GSList *iter)
+GList *
+e_mail_formatter_find_rfc822_end_iter (GList *iter)
 {
 	EMailPart *part;
 	gchar *end;
 
 	part = iter->data;
 	end = g_strconcat (part->id, ".end", NULL);
-	for (; iter != NULL; iter = g_slist_next (iter)) {
+	for (; iter != NULL; iter = g_list_next (iter)) {
 		part = iter->data;
 		if (!part)
 			continue;