Re^4: Clarity in parsing fixed length data.

Parse-FixedLength is a really nice module, and was the leading contender among the three modules when I first went looking. Nice job.

I couldn't tell from the docs if it accepted the "=>" form when using the pack/unpack format specs. We have binary data to read, and I want the name and format columns to line up, so using a ":" separator in a single parameter would have been a problem. With your encouragement I've tested the "=>" and it works fine. It also works in 5.6.1, which is important for us.

I'll put together an example to present to the group at work, and I'm guessing we'll use Parse-FixedLength. Thanks.

Comment on Re^4: Clarity in parsing fixed length data.

Replies are listed 'Best First'.
Re^5: Clarity in parsing fixed length data. by runrig (Abbot) on Aug 16, 2006 at 19:19 UTC
Another thing I like to do when creating a separate class/module for different formats is to add pod to the module to document the details of the format and what the fields are (and their start/end position and length). Then the documentation for the format is just a 'perldoc Something::SomeXFormat' away (and I don't have to hunt for the hardcopy I worked from to create the module) :-) Update: What would be nice is if the code defining the format was actually read from the pod (or vice-versa), so the docs would be self-updating...but I'm not sure about the best way to do that at the moment.	[reply]

Replies are listed 'Best First'.

Re^5: Clarity in parsing fixed length data.
by runrig (Abbot) on Aug 16, 2006 at 19:19 UTC

Update: What would be nice is if the code defining the format was actually read from the pod (or vice-versa), so the docs would be self-updating...but I'm not sure about the best way to do that at the moment.

[reply]