Re: Email::Address::XS

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

* [email protected] [2016-05-28T16:48:40]
> Basically yes. From caller perspective I want to pass email address=20
> object and let Email::MIME to do MIME encoding correctly. Something like=
=20
> this:
>=20
> my $email =3D Email::MIME->create(
> 	header_addr =3D> [ ... ],
> );

I think that requiring people to break headers up even further into to add
a "header_addr" argument is a bit much.  And why header_grps?  How about ob=
ject
that represents the group?  Then the existing header and header_str argumen=
ts
can start silently accepting these objects and doing the right thing.

--=20
rjbs

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

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

iQEcBAEBAgAGBQJXTN4HAAoJEOYby6cMccU5gMkH/3E9VTZn8QbzH0YijU5mzVxh
XLq25RDz77uXDxfAmj0Rcue8q+GM+UAzglx6nBRUkfRQM5l+bPo2h8/w9xD6wqHC
v7o1Ro9/Z9WQh4Fr6A79JYWct4zKSFCaUxp9Rnza+aEcHHNAc94ZuEBRIPKFG9qY
romwZiQggwmKgRxkx9xRjKIpGIC7WVv7sT6qJXKExfZ8id4sJcNf9AlTBL5SSHZK
WeuHyKZ5jPwV55i0Y/+SR0vVy/lZUd7w2S8nTDZFObLl7MU8ItHRlji42CsDU/Vz
8Dnu2hIek8EKOONQ7FvR7d0zciSA+IKVn7nVa5BTBlqi2quCTTSBgNnyQE1xy8c=
=r4m7
-----END PGP SIGNATURE-----

--X1bOJ3K7DJ5YkBrT--