The future of Emacs, Guile, and Emacs Lisp
The future of Emacs, Guile, and Emacs Lisp
Posted Oct 15, 2014 18:04 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)In reply to: The future of Emacs, Guile, and Emacs Lisp by nix
Parent article: The future of Emacs, Guile, and Emacs Lisp
It's mostly used for simple completions and nothing else. IntelliJ products can use their semantic model for smart code refactoring and inspection.
Oh, and CEDET's parser is pitifully inadequate even for plain C, it has no hope of ever understanding C++ completely.
Posted Oct 21, 2014 16:30 UTC (Tue)
by nix (subscriber, #2304)
[Link] (3 responses)
Obviously getting it right for C++ is impossible -- but you need a C++ compiler to understand C++ properly. Actually you need something *better*, because you want to be able to parse incomplete, partially written, and syntactically invalid code as much as possible. That sort of error recovery is *hard*.
Posted Oct 21, 2014 16:36 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link] (2 responses)
Pure C is also not that easy, because lots of C++'s syntactic ambiguity actually comes from C.
Posted Oct 23, 2014 1:34 UTC (Thu)
by cmccabe (guest, #60281)
[Link] (1 responses)
C++ has an undecidable grammar.
I can parse C with yacc. I could never hope to parse C++ with anything but a hand-written parser.
Posted Oct 23, 2014 11:41 UTC (Thu)
by jwakely (subscriber, #60262)
[Link]
int Foo (int i = T<1, int>::i);
(See http://open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#325 for other examples like that)
The future of Emacs, Guile, and Emacs Lisp
The future of Emacs, Guile, and Emacs Lisp
The future of Emacs, Guile, and Emacs Lisp
Details here: http://eli.thegreenplace.net/2007/11/24/the-context-sensi...
The future of Emacs, Guile, and Emacs Lisp