Path: news.ruhr-uni-bochum.de!news.uni-stuttgart.de!news.belwue.de!fu-berlin.de!news.mathworks.com!newsfeed.internetmci.com!news.ac.net!news.serv.net!nntp.teleport.com!usenet
From: Eryq <[email protected]>
Newsgroups: comp.lang.perl.announce,comp.lang.perl.misc
Subject: MIME-parser-1.11 released to CPAN
Followup-To: comp.lang.perl.misc
Date: 25 Jun 1996 21:09:55 GMT
Organization: Little or none...
Lines: 62
Approved: [email protected] (comp.lang.perl.announce)
Message-ID: <[email protected]>
NNTP-Posting-Host: julie.teleport.com
X-Disclaimer: The "Approved" header verifies header information for article transmission and does not imply approval of content.
Xref: news.ruhr-uni-bochum.de comp.lang.perl.announce:358 comp.lang.perl.misc:35179

The latest release of the "MIME-parser" package has been uploaded to the
CPAN under my author id (ERYQ) and name (Eryq).

  * Various small bugs have been found and fixed since 1.10, including
    a bug that kept the trailing \r in header fields in some cases.

  * Thanks to the prodding of Andreas Koenig :-) , this release
    now uses a Makefile.PL.  Be warned: I've only tried the
    installation out under 5.002.  (Since this is the first time
    I've used MakeMaker, please yell at me if I've done
    something stupid...)

Current version:        1.11

------------------------------------------------------------

NAME

   MIME-parser - family of MIME:: modules for parsing MIME messages

DESCRIPTION

   MIME-parser is a collection of Perl5 MIME:: modules for parsing
   and decoding single- or multipart (even nested multipart!) MIME
   messages.

SYNOPSIS

   You start by creating an instance of MIME::Parser, and setting up
   certain parsing parameters: what directory to save extracted files
   to, how to name the files, etc.

   You then give that instance a readable filehandle on which waits a
   MIME message.  If all goes well, you will get back a MIME::Entity
   object, consisting of a MIME::Head (which holds the MIME header
   data) and the name of the file in which the (decoded) body has been
   stored.

   If the original message was a multipart document, the MIME::Entity
   object will have a non-empty list of "parts", each of which is in
   turn a MIME::Entity (which might also be a multipart entity, etc,
   etc...).

   Internally, MIME::Parser asks for instances of MIME::Decoder
   whenever it needs to decode an encoded file.  MIME::Decoder has
   a mapping from supported encodings (e.g., 'base64') to classes
   whose instances can decode them.  You can add to this mapping
   to try out new/experimental encodings.  You can also use
   MIME::Decoder by itself.

AUTHOR

   Eryq, [email protected]
   28 April 1996

--
  ____           __
 / __/__________/_/  Eryq ([email protected])
/ __/ _/ / / , /     Hughes STX, NASA/Goddard Space Flight Cntr.
/___/_/ \  /\  /___
       /_/ /_____/   http://www.mcs.com/~eryq