Summary: | [Scanner] Exit Inclusion occurs too soon | ||
---|---|---|---|
Product: | [Tools] CDT | Reporter: | Sean Evoy <sevoy> |
Component: | cdt-core | Assignee: | Andrew Niefer <aniefer> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P2 | CC: | john.camelon |
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Sean Evoy
2004-08-18 17:19:40 EDT
Because the scanner is 1 token ahead of the parser, when we get the semi colon to complete the FOUND_ME declaration, the scanner immediately gets the next token and encounters the end of the include file and does the callback exitInclusion before the parser processed the semi-colon and does the callback for the variable declaration. The result is that clients think that this variable declaration is happening outside the inclusion instead of being the last thing in the inclusion. What is your proposed solution, oh stealer of defects? This should be fixed for 2.0.1, it will affect more than just Search/Index. fixed in head and 2.0.1 Fix postpones the reporting of callback if we were getting the token one ahead. Verified fixed in cdt 2.0.1 build 20040826 Marking verified for Tanya. |