Re: Email::Address::XS

[pali]

On Sunday 04 September 2016 00:24:56 Ricardo Signes wrote:
> If we never *store* objects, but only produce them as requested, then
> I think the total needed changes are -- but I'm sure I'll miss
> things -- as follows:
> 
> * allow header_str and header args to Email::MIME->create to include
>   objects, which are immediately asked to encode themselves for
>   storage
> * add header_as_obj that takes a header name and, optionally, a class
>   name and offset (an offset so you can ask for an object of the nth
>   Received header)

As prerequisite for offset small change to Email::Simple is needed. 
Currently Email::Simple cannot returns just nth value for header with 
specified name. Support for this is in new pull request: 
https://github.com/rjbs/Email-Simple/pull/16

> * a registry used by header_as_obj to get a default class name from
>   header name

Re: Email::Address::XS

[pali]

On Monday 05 September 2016 10:25:11 p...@cpan.org wrote:
> On Saturday 03 September 2016 18:24:56 Ricardo Signes wrote:
> > The Email::MIME changes look like they could be broken up into
> > several PRs, some of which would be obviously good to apply
> > immediately, like removals of dead code and pointers to bad
> > modules.
> 
> If you think that some of those changes can be merged immediately,
> please specify commits and I create new pull request for them. Btw,
> I'm preparing another big patch series for Encode::MIME::Header
> module (call encode("MIEM-Header", ...)) which will fix remaining
> bugs. So if you know about some in that, let me know ASAP, so I can
> fix it in my patch series ;-)

New Encode was released with my fixes to MIME-Header...
https://metacpan.org/pod/Encode::MIME::Header

> ..Which means that removing pointer to that module will not be
> needed..

Now I created pull request for Email::MIME:
https://github.com/rjbs/Email-MIME/pull/32

It should contains only code cleanup and fixes, no Email::Address::XS... 
Look at it and if there are some problems, let me know!