Groups | Search | Server Info | Login | Register


Groups > perl.pep > #23

Re: Email::Address::XS

Newsgroups perl.pep
Date 2016-08-24 22:55 -0400
Subject Re: Email::Address::XS
Message-ID <20160825025505.GA2164@debian> (permalink)
References (1 earlier) <20160818212128.GA29265@debian> <201608182335.12266@pali> <201608201201.19784@pali> <20160823023439.GB25768@debian> <20160823075624.GB24323@pali>
From perl.pep@rjbs.manxome.org (Ricardo Signes)

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

* pali@cpan.org [2016-08-23T03:56:24]
> > > Also it must be possible to get either named groups from Original-Cc 
> > > header or only list of addresses. And I think with your proposal API it 
> > > is not possible. You would need to call some "downgrade" function and 
> > > then "upgrade" it to another object or so...
> > 
> > Why would this not be possible?  There is some object storing the mailboxes
> > structure, and it provides methods that answer the questions one needs to
> > ask.
> 
> Because you have no idea about arbitrary object. If you want to e.g.
> decode Email::Address::XS object, you must decode only ->phrase() and
> ->comment() parts! Not others.

I don't understand "you have no idea about arbitrary object."  Obviously you
would get a type of object based on the header in question.

> Anyway, lets move forward. I already implemented something and send
> information in email with subject "Email::Simple & Email::MIME with
> Email::Address::XS" to pep mailing list...
> 
> I think this is good approach to provide usable API + ability to extend
> code for other objects...

This reads like, "Look, just use the API that you don't like because I already
wrote some code."  That's not going to sway me.

What happens when someone wants a Date object for the Date header?  Do we add
header_date?  Then header_rcvd for Received headers, and so on?  This interface
leads to either a proliferation of these things or to some line where we say,
"well *these* headers are important enough and *these* are not."  On the other
hand, a generic mechanism is generic.

You can always publish your work as a subclass, if you think it that popular
acclaim will convince me I'm wrong.

-- 
rjbs

Back to perl.pep | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Email::Address::XS pali@cpan.org - 2016-05-23 19:05 +0200
  Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-05-28 16:33 -0400
    Re: Email::Address::XS pali@cpan.org - 2016-05-28 22:48 +0200
      Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-05-30 20:42 -0400
        Re: Email::Address::XS pali@cpan.org - 2016-06-01 18:44 +0200
          Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-06-30 20:51 -0400
            Re: Email::Address::XS pali@cpan.org - 2016-07-03 14:39 +0200
              Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-07-03 19:52 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-07-12 17:43 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-01 19:00 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-08-02 23:03 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-02 18:36 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-08-08 23:41 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-18 17:21 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-08-18 23:35 +0200
                Re: Email::Address::XS pali@cpan.org - 2016-08-20 12:01 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-22 22:34 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-08-23 09:56 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-24 22:55 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-08-25 09:40 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-09-03 18:24 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-09-05 10:25 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-09-11 18:58 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-09-12 09:26 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-09-16 18:37 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-09-18 01:05 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-09-18 11:26 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-09-18 17:40 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-09-28 09:29 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-09-30 12:38 +0200
                Re: Email::Address::XS pali@cpan.org - 2016-11-13 03:17 +0100
                Re: Email::Address::XS pali@cpan.org - 2016-11-13 03:24 +0100
                Re: Email::Address::XS pali@cpan.org - 2017-01-14 21:32 +0100
                Re: Email::Address::XS pali@cpan.org - 2017-01-23 14:44 +0100
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2017-01-28 15:48 -0500
                Re: Email::Address::XS pali@cpan.org - 2017-02-14 21:26 +0100
                Re: Email::Address::XS pali@cpan.org - 2017-03-08 00:03 +0100
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-22 22:26 -0400
                Re: Email::Address::XS pali@cpan.org - 2016-08-23 09:50 +0200
                Re: Email::Address::XS perl.pep@rjbs.manxome.org (Ricardo Signes) - 2016-08-23 09:31 -0400
  Re: Email::Address::XS pali@cpan.org - 2017-02-18 21:25 +0100

csiph-web