http://llvm.org/bugs/show_bug.cgi?id=2583
Summary: Source location not tracked for nested macros
Product: clang
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Semantic Analyzer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Constructs such as
FOO(BAR(m)->abc)
result in error messages like:
FOO(BAR(m)->abc);
^~~
macro.c:18:15: error: no member named 'abc'
while it could ideally be:
FOO(BAR(m)->abc);
~~~~~~ ^
Using macros like this might seem useless but is a very common pattern in
GObject based code (the object system used in GTK+/GNOME). In addition to just
giving clearer error message, it would be useful for a refactoring tool for
GTK+ I'm working on, which would work much better if there was more location
information available for nested macros.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
