Fixed float precision bug while using timestamps as keys #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the timestamps from the input pcap, the float precision used is 6
However, by default perl uses a precision of 5 for usage as a key in a hash
This is problematic when the delta of 2 packets is less then 0.00001, as some of the packets will be overwritten during reading the input file.
I fixed this by first turning the timestamp into a string, using a precision of 6