[cfe-dev] Status of "-parse-print-callbacks"

[Daniel Dunbar]

Hi Jon,
I have just noticed this as well; I believe this is a recent regression. I'm
about to file a bug...

 - Daniel

On Tue, Mar 24, 2009 at 12:42 AM, Jon Simons <simonsj at ccs.neu.edu> wrote:

> I am wondering, what is the status of using the "-parse-print-callbacks"
> flag for clang-cc?
>
> Should it succeed and fail when normal parsing would succeed and fail?
>
> I ask because I see discrepancies:
>
>   # cat test.c
>   typedef struct foo { int x; } foo;
>   void test() {
>     foo *foo;
>     foo->x = 0;
>   }
>   # clang-cc test.c
>   # clang-cc -parse-print-callbacks test.c 1>/dev/null
>   test.c:4:6: error: expected identifier or '('
>     foo->x = 0;
>        ^
>   test.c:4:6: error: parse error
>   2 diagnostics generated.
>
> Is this something that warrants a PR and/or following up on?  Or is
> "-parse-print-callbacks" something that might not be worth updating
> because C++ parsing is still in development?
>
>
> Just Curious,
> -Jon Simons
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20090324/0a730905/attachment.html>