Well, in an editor, there some operations that operate on solely on a file, and some at the project level. I would make sense to me if typechecking errors were reported against the original file (following the pragmas) while lexing and outlining results would operate without (on the actual file contents).
JP On Fri, Sep 10, 2010 at 2:13 PM, Antoine Latter <aslat...@gmail.com> wrote: > On Fri, Sep 10, 2010 at 1:40 AM, JP Moresmau <jpmores...@gmail.com> wrote: > > Hello fellow Haskellers, > > In EclipseFP we use the GHC API for IDE related stuff like syntax > > highlighting and code outlines. However, I ran into something funny > > yesterday: when a source file contains LINE pragmas > > ( > http://www.haskell.org/ghc/docs/6.12.2/html/users_guide/pragmas.html#line-pragma > ), > > all the locations for tokens are changed to reflect the pragmas > information. > > While this is great in the "normal' GHC usage, this is not so great for > us, > > because we're interested in that source code, not in original code. I > > haven't seen any flag to turn that behavior off in the docs, nor in the > > Lexer code, but have I missed something? Can I tell GHC to just ignore > these > > pragmas? I suppose even using GHC for building and something else > > (haskell-src-exts?) for code handling would leave us with compilation > > messages at the wrong place. > > Thanks, > > Would you turn the behavior back on when editing .hsc files or > something similar? > -- JP Moresmau http://jpmoresmau.blogspot.com/
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
