search for: macrodecl

...cessor to notify the parser each time one of the above directives occurs. These are the callbacks that should be implemented: "MacroDefined", "MacroUndefined", "FileChanged", and "InclusionDirective". AST will be extended to support two new DECL types: "MacroDecl" and "FileIncludeDecl". Where "FileIncludeDecl" AST might contain other "FileIncludeDecl"/"MacroDecl" ASTs. These two new AST DECLs are not part of TranslationUnitDecl and are handled separately (see AST example below). In the LLVM IR, metadata debug in...

...cessor to notify the parser each time one of the above directives occurs. These are the callbacks that should be implemented: "MacroDefined", "MacroUndefined", "FileChanged", and "InclusionDirective". AST will be extended to support two new DECL types: "MacroDecl" and "FileIncludeDecl". Do we really need to touch the AST? Or would it be reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) Where "FileIncludeDecl" AST might contain other &quot...

...cessor to notify the parser each time one of the above directives occurs. These are the callbacks that should be implemented: "MacroDefined", "MacroUndefined", "FileChanged", and "InclusionDirective". AST will be extended to support two new DECL types: "MacroDecl" and "FileIncludeDecl". Do we really need to touch the AST? Or would it be reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) Where "FileIncludeDecl" AST might contain other &quot...

...cessor to notify the parser each time one of the above directives occurs. These are the callbacks that should be implemented: "MacroDefined", "MacroUndefined", "FileChanged", and "InclusionDirective". AST will be extended to support two new DECL types: "MacroDecl" and "FileIncludeDecl". Do we really need to touch the AST? Or would it be reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) Where "FileIncludeDecl" AST might contain other &quot...

...the above directives > occurs. > > These are the callbacks that should be implemented: > > "MacroDefined", "MacroUndefined", "FileChanged", and "InclusionDirective". > > > > AST will be extended to support two new DECL types: "MacroDecl" and > "FileIncludeDecl". > > > > Do we really need to touch the AST? Or would it be reasonable to wire up > the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps > it is already wired up for other reasons?) > > > > Where &quo...

...s. >> >> These are the callbacks that should be implemented: >> >> "MacroDefined", "MacroUndefined", "FileChanged", and "InclusionDirective". >> >> >> >> AST will be extended to support two new DECL types: "MacroDecl" and >> "FileIncludeDecl". >> >> >> >> Do we really need to touch the AST? Or would it be reasonable to wire up >> the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps >> it is already wired up for other reasons?) &g...

...llbacks that should be implemented: >>> >>> "MacroDefined", "MacroUndefined", "FileChanged", and >>> "InclusionDirective". >>> >>> >>> >>> AST will be extended to support two new DECL types: "MacroDecl" and >>> "FileIncludeDecl". >>> >>> >>> >>> Do we really need to touch the AST? Or would it be reasonable to wire up >>> the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps >>> it is already wir...