This extends the set of resources parsed by llvm-rc by DIALOG and DIALOGEX.
Additionally, three optional resource statements specific to these two resources are added: CAPTION, FONT, and STYLE.
Paths
| Differential D36905
[llvm-rc] Add DIALOG(EX) parsing ability. [5/8] ClosedPublic Authored by mnbvmar on Aug 18 2017, 3:48 PM.
Details Summary This extends the set of resources parsed by llvm-rc by DIALOG and DIALOGEX. Additionally, three optional resource statements specific to these two resources are added: CAPTION, FONT, and STYLE.
Diff Detail
Event Timeline
mnbvmar added a child revision: D37021: [llvm-rc] Add VERSIONINFO parsing ability. [6/8].Aug 22 2017, 1:45 PM Comment Actions Code looks good, I just have some testing suggestions.
This revision is now accepted and ready to land.Aug 23 2017, 1:11 PM
mnbvmar retitled this revision from [llvm-rc] Add DIALOG(EX) parsing ability. to [llvm-rc] Add DIALOG(EX) parsing ability. [5/8]. Comment ActionsRebased the code; addressed ecbeckmann's comment. Closed by commit rL312009: [llvm-rc] Add DIALOG(EX) parsing ability (parser, pt 5/8). (authored by mnbvmar). · Explain WhyAug 29 2017, 9:53 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 112398 llvm/test/tools/llvm-rc/Inputs/parser-correct-everything.rc
llvm/test/tools/llvm-rc/Inputs/parser-dialog-cant-give-helpid.rc
llvm/test/tools/llvm-rc/Inputs/parser-dialog-too-few-args.rc
llvm/test/tools/llvm-rc/Inputs/parser-dialog-too-many-args.rc
llvm/test/tools/llvm-rc/Inputs/parser-dialog-unknown-type.rc
llvm/test/tools/llvm-rc/Inputs/parser-dialog-unnecessary-string.rc
llvm/test/tools/llvm-rc/parser.test
llvm/tools/llvm-rc/ResourceScriptParser.h
llvm/tools/llvm-rc/ResourceScriptParser.cpp
llvm/tools/llvm-rc/ResourceScriptStmt.h
llvm/tools/llvm-rc/ResourceScriptStmt.cpp
|
Does llvm-rc report a source location along with its error? Checking source location reports with FileCheck has always been quite brittle, so we definitely don't want to check for that in all of these tests, but we should have one test for accurate error locations.