Re: Email::Address::XS

--3V7upXqbjpZ4EhLz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* [email protected] [2016-09-17T19:05:51]
> $class->from_mime_string() will take raw MIME encoded string and returns=
=20
> new object of $class (which will have decoded string parts)
> $object->as_mime_string() will convert (Unicode) $object into raw MIME=20
> encoded string
>=20
> It is OK for you?

That all sounded fine.  I think the paragraph I left quoted overspecifies a
bit.  Whether the object is storing things decoded or not isn't any of our
concern as long as it has those two methods.  But I think we're on the same
page.

The Email::Address::XS use should be optional, as right now people can
install Email::MIME in an compiler-free environment.  We can add it as a
recommended prereq.

--=20
rjbs

--3V7upXqbjpZ4EhLz
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJX3rITAAoJEOYby6cMccU579EH/118XfKrsdoA+mZXkARdtJt+
g9MBniy15o9KywbhBtvJGL1Bhp2pfjNZfKmWlf/bB9MYSRHmlluVSHdAA+h5Gfjg
540W2fUiKZWcJuYedyuz+glX8qPzSomrjNg4pnNh+lP6l6LhHFc2bXqjgfAhGTcx
hIL8iXaR+yajgqGMPxO+sJSBiAAnZnwVsQZV+4CaPRcetAKrUGUmFyHXvxOZxVKD
IVFky6FOPPvuvAJCAKRj8ii61ItueJAVzBZp8sf1KESN4GkKXs5nZ154uwQq1h6C
oMibWJkDFIEyBfG7B/nJAJA8EN5Y3zv5L8VvvYJ4fVr9aTIB4zbHsVp+aviajbo=
=UXRT
-----END PGP SIGNATURE-----

--3V7upXqbjpZ4EhLz--