Ignore-this: c3325b39b0a133af55203348aaba6cde

darcs-hash:061d303cbdc6ea286f4233f09eeca346f15c7745

Ignore-this: aa004ca68ad9180237512e1cab94aa3d

darcs-hash:98ac3f80764d34ad5d514cfed87ca9413be8feae

Ignore-this: a2e9a3db24f62886a0410cb6a77e50b9

darcs-hash:3d0b1d18b470e1f25e3cc86a9b816eea312aab55

Test suite was referencing the old rfc2388, and used names that would
conflict with normal rfc2388 if someone decided to use both in the
same image

darcs-hash:45050ee6b1596312923bfc5d5ddfff93368d60a6

Change the random tester to create characters which have a much higher probability of causing parser errors

darcs-hash:5d106d807f14fa9c002d1c4cfeb49c9e0f85fbb0

You'd never guess, but occasionally the data we get back is different
than the data we sent in :(

darcs-hash:5f85b97b1687398efb385ec50a93a8e2b5c07947

Use (asdf:component-pathname (asdf:find-system :rfc2388.test)) instead of *compile-file-pathname* for locating the test data directory

darcs-hash:5229e7ea58eaaa02490ca9368ea6ca65a35391f9

darcs-hash:cf59b7d92696eb7ed045c173fdef93bcf533f695

darcs-hash:d80d4f48a7f0ec45e7cec18691bb65e1b8d94b54

darcs-hash:0793249770b4ec43dab7604c43622690e4bef8ba

darcs-hash:6a03e0755245939d581911ebe432d9f8e7299ba8

darcs-hash:e078dedb5bc15e905cea3876d6989ad08c5a676d

darcs-hash:ac5b11e6a9eaea8b49182db036f89ee8cf7b549c

darcs-hash:6cc76bf971460f28d76fdf771f51dbe7dce19693

darcs-hash:d2bac304461dd6403e49e613f659c326c122f16f

PARSE-MIME now has the same api as the original PARSE-MIME (including
support for :write-to-file), READ-MIME now does what PARSe-MIME used
to do (and has the same source+boundray+callback API).

darcs-hash:ae94cbcc3759b39f4f903180db243781d89e60bc

darcs-hash:2b8cd7c0e0d3f4af93ba8e8f679f6e6a26c1e339

darcs-hash:8f6f2656c3b25f0416768547c6685dc514a073d1

darcs-hash:88496ef28779741083cf24a3775a54692bd89e80

darcs-hash:c0f7a7f4617627353328343a16ee32f5a5a7c436