tag:blogger.com,1999:blog-203063759820106893.post4454268289190566677..comments2023-03-25T08:30:26.602-04:00Comments on A Moment of Zen: GMime 2.3.0Jeffrey Stedfasthttp://www.blogger.com/profile/12271561115384429651noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-203063759820106893.post-33420852611802060952008-05-29T14:01:00.000-04:002008-05-29T14:01:00.000-04:00oh, yes, with that I'd agree ;-)oh, yes, with that I'd agree ;-)Jeffrey Stedfasthttps://www.blogger.com/profile/12271561115384429651noreply@blogger.comtag:blogger.com,1999:blog-203063759820106893.post-69419322782374344322008-05-29T13:31:00.000-04:002008-05-29T13:31:00.000-04:00goffset is always just:typedef gint64 goffset;so, ...goffset is always just:<BR/><BR/>typedef gint64 goffset;<BR/><BR/>so, gint64 works as good as goffset. However imho using goffset is nicer as a documentation aspect.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-203063759820106893.post-90087623779270975492008-05-29T13:10:00.000-04:002008-05-29T13:10:00.000-04:00Thanks Joe - my guess is that Beagle is also proba...Thanks Joe - my guess is that Beagle is also probably the only consumer of GMime-Sharp so far - but that may change, so I might as well try to make the API suck less ;)<BR/><BR/>Looks like Beagle doesn't use the sucky parts of the API, so it probably won't be affected except for maybe a few slight changes.<BR/><BR/>InternetAddressList.ParseString() - should this maybe be renamed to InternetAddressList.Parse()? Would that be more consistent with .NET's APIs?<BR/><BR/>Alex: any reason to use goffset over gint64? Only reason I'm using gint64 right now is that my glib does not have goffset and I figure if mine doesn't, then it is unlikely that my target audience will have it.<BR/><BR/>Honestly, I'd also like to kep the GLib requirement for GMime as old as possible (configure currently checks for >= 2.0.0 but I might need 2.2, but afaik, I don't need anything newer than that currently so it seems silly to bump the requirement to GLib-2.14, just for goffset.Jeffrey Stedfasthttps://www.blogger.com/profile/12271561115384429651noreply@blogger.comtag:blogger.com,1999:blog-203063759820106893.post-7557152148650094842008-05-29T12:38:00.000-04:002008-05-29T12:38:00.000-04:00AFAIK Beagle is the only consumer of the gmime-sha...AFAIK Beagle is the only consumer of the gmime-sharp bindings, although things may have changed in the last year or so.<BR/><BR/>I'd suggest taking a look at how Beagle uses it, most notably the mail filter here:<BR/><BR/><A HREF="http://svn.gnome.org/svn/beagle/trunk/beagle/Filters/FilterMail.cs" REL="nofollow">http://svn.gnome.org/svn/beagle/trunk/beagle/Filters/FilterMail.cs</A><BR/><BR/>and the Evolution mail backend here:<BR/><BR/><A HREF="http://svn.gnome.org/svn/beagle/trunk/beagle/beagled/EvolutionMailQueryable/EvolutionMailIndexableGenerator.cs" REL="nofollow">http://svn.gnome.org/svn/beagle/trunk/beagle/beagled/EvolutionMailQueryable/EvolutionMailIndexableGenerator.cs</A><BR/><BR/>Hope this helps!<BR/>JoeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-203063759820106893.post-39276287366135716362008-05-29T11:24:00.000-04:002008-05-29T11:24:00.000-04:00Dude, you need to use goffset (in recent glib) ins...Dude, you need to use goffset (in recent glib) instead of gint64.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-203063759820106893.post-7427960052530609592008-05-29T10:15:00.000-04:002008-05-29T10:15:00.000-04:00Congrats.Congrats.Sankarhttps://www.blogger.com/profile/13337547916077401549noreply@blogger.com