Re: Print column numbers when compiling
Anthony Ramine <[email protected]>
| Newsgroups | gmane.comp.lang.erlang.patches |
|---|---|
| Message-ID | <[email protected]> |
Another branch that may interest you is parse-ranges, which uses scan-end-location to compute start and end locations of each node in the AST. I also have a work in progress branch which let epp also track any macro expansion and keep their respective locations. -- Anthony Ramine Le 13 nov. 2013 à 13:56, Anthony Ramine <[email protected]> a écrit : > See my scan-end-location branch :) > > I also have an epp-read-lines branch which allows a tool builder to ask epp to print specific lines of parsed files. > > Final objective is Clang-like diagnostics. > > -- > Anthony Ramine > > Le 13 nov. 2013 à 11:37, Thomas Järvstrand <[email protected]> a écrit : > >> I just tried this patch out yesterday. I would like to ask why, if you're going to all this trouble, do you not also include information about the end of each token as well as the start? From a toolbuilder's perspective it would make this patch immensely more useful. Just a couple of examples would be when building Erlang backends for refactoring tools or context sensitive autocompletion in the editor. > _______________________________________________ erlang-patches mailing list [email protected] http://erlang.org/mailman/listinfo/erlang-patches