{"action":"closed","issue":{"url":"https://api.github.com/repos/openEHR/adl-antlr/issues/15","labels_url":"https://api.github.com/repos/openEHR/adl-antlr/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/openEHR/adl-antlr/issues/15/comments","events_url":"https://api.github.com/repos/openEHR/adl-antlr/issues/15/events","html_url":"https://github.com/openEHR/adl-antlr/issues/15","id":112790583,"number":15,"title":"Small possible improvements to make parsing easier","user":{"login":"pieterbos","id":21126,"avatar_url":"https://avatars.githubusercontent.com/u/21126?v=3","gravatar_id":"","url":"https://api.github.com/users/pieterbos","html_url":"https://github.com/pieterbos","followers_url":"https://api.github.com/users/pieterbos/followers","following_url":"https://api.github.com/users/pieterbos/following{/other_user}","gists_url":"https://api.github.com/users/pieterbos/gists{/gist_id}","starred_url":"https://api.github.com/users/pieterbos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pieterbos/subscriptions","organizations_url":"https://api.github.com/users/pieterbos/orgs","repos_url":"https://api.github.com/users/pieterbos/repos","events_url":"https://api.github.com/users/pieterbos/events{/privacy}","received_events_url":"https://api.github.com/users/pieterbos/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-22T12:16:23Z","updated_at":"2015-10-29T14:24:24Z","closed_at":"2015-10-29T14:24:24Z","body":"I made some small adaptations to your parser to make parsing just that little bit easier. This does not improve the functionality of the parser, only the usability.\r\n\r\nSee https://github.com/nedap/archie/commit/0109786d8110addb562c2bf049c0475041e31efc\r\n\r\n- you changed some Lexer tokens to strings in the metadata section. This means i now have to match the actual string in java-code to match this. Changed it to named parser rules so i can use those\r\n- added a SEMICOLON lexer token, So that can be used in the parsing of terminology code constraints with assumed values. Could also be solved (perhaps better?) with a different parser rule\r\n- c_string now directly has a STRING instead of a string_value. Same content, but not consistent with the rest of the grammar and therefore can require some extra code.\r\n"}}