aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2017-10-06 22:05:15 +0000
committerZachary Turner <zturner@google.com>2017-10-06 22:05:15 +0000
commita92eb33ad59e3d01bd832f9c19a03d011f393a92 (patch)
treef22d4e1130854f98ad16609ddff84856c380c599 /clang/lib/Frontend/CompilerInvocation.cpp
parent9d8b358a49bec7cbd225062962d7959854d04338 (diff)
downloadllvm-a92eb33ad59e3d01bd832f9c19a03d011f393a92.zip
llvm-a92eb33ad59e3d01bd832f9c19a03d011f393a92.tar.gz
llvm-a92eb33ad59e3d01bd832f9c19a03d011f393a92.tar.bz2
[llvm-rc] Implement escape sequences in .rc files.
This allows the escape sequences (\a, \n, \r, \t, \\, \x[0-9a-f]*, \[0-7]*, "") to appear in .rc scripts. These are parsed and output in the same way as it's done in original MS implementation. The way these sequences are processed depends on the type of the resource it resides in, and on whether the user declared the string to be "wide" or "narrow". I tried to maintain the maximum compatibility with the original tool (and fail in some erroneous situations that are accepted by .rc). However, there are some (extremely rare) cases where Microsoft tool outputs nonsense. I found it infeasible to detect such casses. Patch by Marek Sokolowski Differential Revision: https://reviews.llvm.org/D38426 llvm-svn: 315118
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions