symbol lookup and overload resolution
Stefan Seefeld <[email protected]>
| Newsgroups | gmane.comp.documentation.synopsis |
|---|---|
| Message-ID | <[email protected]> |
hi there, I'v been working on symbol lookup in the C++ parser, and my focus is more and more shifted towards type analysis and overload resolution. Realising what big a topic that is, my current thinking is that I could put that into another module, and let symbol lookup return symbol sets of (possibly) overloaded (function) names. The primary reason is that symbol lookup as such is almost complete, in particular, the current state of symbol lookup is sufficient to fix the existing issues with the parser (i.e. resolving ambiguities in the grammar that require a little type analysis). Further, it seems the present functionality is already enough to rewrite the python binding for the C++ parser. Real overload resolution is currently only required to produce correct cross references in the code view (i.e. SXR for example). Does anybody see potential problems with such a separation between symbol lookup and overload resolution (and probably more high level analysis) ? I take this occasion to encourage everybody to get involved into the development of synopsis. With relatively little efford it will be possible to use the redesigned parser for more advanced things that I will try to integrate into the synopsis framework step by step, such as code generation and various forms of code analysis beyond the documentation extraction that synopsis is currently used for. Now is also a good time to suggest enhancements and report bugs that I should consider when thinking about the next release. Kind regards, Stefan