• marja's avatar
    [strong] Declaration-after-use errors. · 1eddcf5b
    marja authored
    We cannot yet detect use-before-declaration in general, because for that we'd
    need to analyze the context when compiling. But we can detect an error case
    where we first see a use, then a declaration.
    
    For this, I also added end position tracking (needed for error messages) to
    VariableProxy.
    
    Note: the position naming is completely inconsistent: start_position &
    end_position, position & end_position, pos & end_pos, beg_pos & end_pos, to name
    a few. This doesn't fix all of it, but tries to unify towards start_position &
    end_position whenever possible w/ minimal changes.
    
    BUG=
    
    Review URL: https://codereview.chromium.org/943543002
    
    Cr-Commit-Position: refs/heads/master@{#26880}
    1eddcf5b
Name
Last commit
Last update
benchmarks Loading commit data...
build Loading commit data...
include Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
Makefile.nacl Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...