I wrote a decoder that reads binary telegrams (or messages) with different types (meaning different structures) from a log file.
For each telegram type the table has an unpack template that defines the structure of the telegram and a list of names for its fields.
The structure is unpacked and the values are formatted with their names to make a readable string representation describing the content of the telegrams.
Currently this works well with simple types and single arrays prefixed with their length. The structure of the telegrams are given and part of an interface.
I agree, there could be simpler unified packings, but that is what I have to deal with.
Maybe it is a good idea to allow 'two step unpacking', in order to enable the decoding of more complex structures. Thanks, I have to think about it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
