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).<div>
<br></div><div>JP<br><br><div class="gmail_quote">On Fri, Sep 10, 2010 at 2:13 PM, Antoine Latter <span dir="ltr"><<a href="mailto:aslatter@gmail.com">aslatter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Fri, Sep 10, 2010 at 1:40 AM, JP Moresmau <<a href="mailto:jpmoresmau@gmail.com">jpmoresmau@gmail.com</a>> wrote:<br>
> Hello fellow Haskellers,<br>
> In EclipseFP we use the GHC API for IDE related stuff like syntax<br>
> highlighting and code outlines. However, I ran into something funny<br>
> yesterday: when a source file contains LINE pragmas<br>
> (<a href="http://www.haskell.org/ghc/docs/6.12.2/html/users_guide/pragmas.html#line-pragma" target="_blank">http://www.haskell.org/ghc/docs/6.12.2/html/users_guide/pragmas.html#line-pragma</a>),<br>
> all the locations for tokens are changed to reflect the pragmas information.<br>
> While this is great in the "normal' GHC usage, this is not so great for us,<br>
> because we're interested in that source code, not in original code. I<br>
> haven't seen any flag to turn that behavior off in the docs, nor in the<br>
> Lexer code, but have I missed something? Can I tell GHC to just ignore these<br>
> pragmas? I suppose even using GHC for building and something else<br>
> (haskell-src-exts?) for code handling would leave us with compilation<br>
> messages at the wrong place.<br>
> Thanks,<br>
<br>
</div></div>Would you turn the behavior back on when editing .hsc files or<br>
something similar?<br>
</blockquote></div><br><br clear="all"><br>-- <br>JP Moresmau<br><a href="http://jpmoresmau.blogspot.com/">http://jpmoresmau.blogspot.com/</a><br>
</div>