emlcontentfoo: drop the {discrete} and {composite} fields

[public-inbox.git] / lib / PublicInbox / EmlContentFoo.pm

diff --git a/lib/PublicInbox/EmlContentFoo.pm b/lib/PublicInbox/EmlContentFoo.pm
index e6005d290c933b1575bdc795123b6c1ae67ccc79..c163eaf5183d4a8372be578b0a0ec23e05bcb4bd 100644 (file)
--- a/lib/PublicInbox/EmlContentFoo.pm
+++ b/lib/PublicInbox/EmlContentFoo.pm
@@ -102,11 +102,6 @@ sub parse_content_type {
                type       => $type,
                subtype => $subtype,
                attributes => $attributes,
-
-               # This is dumb.  Really really dumb.  For backcompat. -- rjbs,
-               # 2013-08-10
-               discrete   => $type,
-               composite  => $subtype,
        };
 }
 
@@ -301,11 +296,6 @@ This routine parses email content type headers according to section 5.1 of RFC
 a hash as above, with entries for the C<type>, the C<subtype>, and a hash of
 C<attributes>.
 
-For backward compatibility with a really unfortunate misunderstanding of RFC
-2045 by the early implementors of this module, C<discrete> and C<composite> are
-also present in the returned hashref, with the values of C<type> and C<subtype>
-respectively.
-
 =func parse_content_disposition
 
 This routine is exported by default.