8 Sep
2010
8 Sep
'10
7:38 a.m.
Hi, On Sun, Sep 5, 2010 at 2:45 AM, Dave Abrahams <dave@boostpro.com> wrote:
emacs, vi, and VS only make local decisions about each symbol. You ought to be able to do much better by taking in an entire file and throwing out the possibilities that result in invalid parses. I know this approach works for natural language, which is full of the same kinds of ambiguities (homonyms/homophones). Actually the NLP case is much harder because a word doesn't have to be used consistently across sentences.
FYI, there is an GCCSense project(http://cx4a.org/software/gccsense/) to use with emacs/vim for translation unit aware code completion. Best regards, -- Ryo IGARASHI, Ph.D. rigarash@gmail.com