Yup, but I like the memorable-self-documenting-english-worded-ness of the api ...
It's a pretty incomplete API. You didn't even support the integer formats used by most communication protocols.
As for memorable and self-documenting, all that's needed here is
sub parse_myformat_rec { ... }
That would be more meaningful and surely at least 10 times faster. If so, that's the difference between 6 seconds and 60 seconds when processing large files as is usually the case with such code.
I can't guess how it gets twisted across platforms so I leave it as is
So why did you go out of your way to write code that will read your integers on those platforms?
perlpacktut recommends Convert::Binary::C :) I find "my api" (similar to what I saw in javascript/java/c#sharp ...) easier
perlpacktut recommends Convert::Binary::C for C structs. Your API isn't easier at handling those; it's completely useless at handling alignment.
In reply to Re^4: Iteratively unpack structure from binary file ( ReadBytes, ReadFloat, ReadInt32 )
by ikegami
in thread Iteratively unpack structure from binary file
by cMonkE
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |