I maintain a
module whose test suite contains binary data. I put the data in a separate
data directory and list each file in the
MANIFEST file. No trouble at all.
However, I had trouble with endianness. Your module should be endian-aware if it is to interpret the binary data. See Numbers endianness and Width in perlport.
Note that before perl 5.9.2 there was apparently no direct way to specify explicit interpretation (endianness) for numbers other than int and short (See the modifiers n, N, v and V to unpack). Of course, there are ways around this, e.g. to reverse the input to unpack depending on endianness.
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.