3 ms·
No. (You need parse all includes to know typedefs, but that's it.) C++ is awkward for a different reason, but there's nothing unparseable about it. Resolving t
by kivikakk 13y ago
No. (You need parse all includes to know typedefs, but that's it.)
C++ is awkward for a different reason, but there's nothing unparseable about it. Resolving types for tab completion/hinting is getting closer to static analysis (at least, with C++ it is), but parsing is well and truly done by that stage.
There's nothing about template<4> that can't be parsed, and nothing about the templates or instantiations thereof causes the syntax to be interpreted differently; this is probably the requirement for a parser to be Turing complete.
Perl is actually unparseable without execution: you can modify the allowed syntax mid-parse, based on some condition known only at runtime. Nothing about a template argument (for example) in some call causes a later template definition to be interpreted according to different syntax rules.
- 0x0 13y agoMakes perfect sense, and I see they're not the same now. Thanks for the explanation! :)
- ExpiredLink 13y ago> C++ is awkward for a different reason, but there's nothing unparseable about it. Some corner cases in C++ are ambiguous. Those are 'resolved' by guessing what may be more suitable in the current context.