Both the other replies look like they'll work! I'd advise taking either of them, and turning them into a function that takes in the text to encode and the maximum length, and either returns the correctly-encoded string, or does a
die on error. Something like (modifying
jwkrahn's version):
use constant MaxMessageLength => 300_000;
sub stx_encode {
my ($Message, $max_length) = @_;
my $MsgLgth = 18 + length $Message;
die "Formatted message exceeds MaxMessageLength" if $MsgLgth >= $max
+_length;
return sprintf "\x2%08d00000000%s\x3", $MsgLgth, $Message;
}
print stx_encode('hello', MaxMessageLength);
The benefit of making a function is it's more widely reusable, and is generally better practice as one can write (and test) each piece of a program bit by bit.
Edit: and creating
stx_decode would be an obvious step, and then you'd have two little functions that nicely wrap that format.
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.