MIME-Version: 1.0
In-Reply-To: <878wdrtde3.fsf@yoom.home.cworth.org>
References: <1258851430-28732-1-git-send-email-chris@chris-wilson.co.uk>
	<87einkqeyt.fsf@yoom.home.cworth.org>
	<1259329997-sup-2634@broadwater.alporthouse.com>
	<878wdrtde3.fsf@yoom.home.cworth.org>
Date: Fri, 27 Nov 2009 23:58:02 -0600
Message-ID: <935ead450911272158h56c68382v7b8f479cf9fa8256@mail.gmail.com>
From: Jeffrey Ollie <jeff@ocjtech.us>
To: Carl Worth <cworth@cworth.org>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] [PATCH] notmuch-new: Eliminate tallocs whilst
	construct filenames.
Precedence: list

On Fri, Nov 27, 2009 at 11:41 PM, Carl Worth <cworth@cworth.org> wrote:
>
> But yes, we need a test suite.

I have zero experience, but Check[1] looks interesting.

> Oh, and we'll also need to deal with remaining glib usage inside of
> notmuch, (and inside of GMime as well), before we can do good testing
> for memory-fault injection. Maybe what we'll end up with is a patch to
> de-glib-ify GMime? I'm not sure.

Rather than de-glib-ify'ing GMime wouldn't it be better to find a non
glib-based library for MIME processing?  I do most of my development
in Python these days so I don't know of any examples.  My googling
turned up several C++ libraries or c-client and I wouldn't want to go
down either of those paths.

[1] http://check.sourceforge.net/

-- 
Jeff Ollie