Format Locations according to GNU conventions#6
Open
ellerh wants to merge 1 commit intoRavenbrook:masterfrom
Open
Format Locations according to GNU conventions#6ellerh wants to merge 1 commit intoRavenbrook:masterfrom
ellerh wants to merge 1 commit intoRavenbrook:masterfrom
Conversation
* basics/_location.sml (to_string, extract_components): Use FILE:LINE1.COLUMN1-LINE2.COLUMN2 instead of FILE:LINE1,COLUMN1 to FILE:LINE2,COLUMN2 to comply with GNU standards.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
There's hardly a reason to invent another format for error locations.
Using the GNU format has the advantage that Emacs and other tools
support it out of the box.
FILE:LINE1.COLUMN1-LINE2.COLUMN2 instead of
FILE:LINE1,COLUMN1 to FILE:LINE2,COLUMN2 to comply with GNU standards.