You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Character positions on most language features can be offset by a few to the right. This comes from preprocessing adding a public access specifier when non is provided.
Possible solution:
Calculate the difference in string length from a line before and after preprocessing. After which the difference can be subtracted from the character position. If a access specifier is added in preprocessing the character position is offset to the correct location. If no keyword is added the lines are equal in length and no offset is required.
note: After some thought i won't be implementing this until tabs are supported (PR #29). Because it would need a refactor after merging.
The text was updated successfully, but these errors were encountered:
Bug:
Character positions on most language features can be offset by a few to the right. This comes from preprocessing adding a public access specifier when non is provided.
Possible solution:
Calculate the difference in string length from a line before and after preprocessing. After which the difference can be subtracted from the character position. If a access specifier is added in preprocessing the character position is offset to the correct location. If no keyword is added the lines are equal in length and no offset is required.
note: After some thought i won't be implementing this until tabs are supported (PR #29). Because it would need a refactor after merging.
The text was updated successfully, but these errors were encountered: