Parser compatibility fixes #674
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Details: * Both comma and space accepted as separators. * Tolerating trailing separator Updated copyright notice formatting + year.
Now tolerating botched forset lines like "forset12,34,56". All 3 nodes (12,34,56) must be accepted for backwards compatibility.
Now tolerates duplicate separators - quite a common occurence in old truckfiles.
|
👍 But the parser also fails at parsing the hooks and lockgroups of this truck ISOcontainers. I think we must always allow trailing separators (concluding comments). |
Yeah. * sigh * |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #502