Fellow Monks,

The problem is MIME::Base64 decode(?) results under activestate Perl. The file size after the decode is always different (bigger than the original file): 
use MIME::Base64;

open my $reader, "TEST.gif";

while (read($reader, $buffer, 10*57)) {
   $file_data .= decode_base64(encode_base64($buffer, ''))
}

open my $writer, ">TEST_base64.gif";
print $writer $file_data;

__END__

`dir` output:
11/24/2005  03:13 AM            66,072 TEST.gif
04/16/2006  09:28 PM            66,437 TEST_base64.gif

[download]

This is `perl -v`: 
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 25 registered patches, see perl -V for more detail)

[download]


In reply to ActivePerl MIME::Base64 bug? by sh1tn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.