Not forgotten.
IMHO, you don't need that conversion at all, unless
there is another reason/problem. Perl has no trouble
with a string like the first $gif in your code.
Why would you want an extra conversion step? Maybe
you like to dump the hex-string on a terminal, readible
to the human eye? Insert it in an e-mail (base64 would be
better in that case)? Does the database only accept ASCII
strings (BerkeleyDB eg does accept them)?
But if you just want to redirect the data in a perlish way,
just keep with the unconverted 1-byte wide strings.
Jeroen
"We are not alone"(FZ)
Update: epoptai CB'd me an alternative
explanation of the posting, that makes more sense.
His code will do. But, consider
pack 'u*', $gif;, CGIPack or
MIME::Base64 to pack
your strings, as that shortens the strings somewhat.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.