Call it reverse engineering the book. Larry has a base64-to-uuencode converter in the cammel book, and I needed the reverse so I could build a client to the Velar Central Archive. So here's a few subroutines I built to help out. (And unlike mhttpd, it's more perl translating than looping)
# Convert data to base64
sub base64 {
    my($line)=@_;
    my($r);

    $r=pack "u",$line;
    $r=~ s/^.(.+)$/$1/;
    $r=~ tr# -_#A-Za-z0-9+/#;
    return $r;
}

# base64 back to reality
sub unbase64 {
    my($line)=@_;
    my($r);
    
    $line =~ tr#A-Za-z0-9+/##cd;
    $line =~ tr#A-Za-z0-9+/# -_#;
    $r=pack("c", 32 + 0.75*(length $line));
    return unpack("u", $r . $line);
}

[download]

In reply to Base64 by the (cammel) book by strredwolf

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.