Re: Re: Synopsis roadmap
Stefan Seefeld <[email protected]>
| Newsgroups | gmane.comp.documentation.synopsis |
|---|---|
| Message-ID | <[email protected]> |
David Abrahams wrote: > Stefan Seefeld <[email protected]> writes: > > >>Douglas Gregor wrote: >> >> >>>The best reference for this is our Implementing Concepts paper, >>>available at: >>> http://www.osl.iu.edu/~dgregor/ConceptGCC/papers/index.html >>>There's also an updated and much-improved version of the concepts >>>proposal there. >> >>Found it, thanks a lot ! > > > So, how about it? It is getting a bit urgent for us to have this > functionality. If I can help in any way, I'd be willing. Could you (or Doug) please summarize what you expect synopsis to do when it encounters such code ? Adding productions to accept the syntax is (almost) straight forward, but doing even the least bit of semantic analysis is not. As you may know, the old parser has some trouble with slightly 'advanced' C++ code, which made me start to rewrite it entirely. (Looking back now, I wonder how it managed to produce any useable results on things like boost's libraries at all.) While I feel I make good progress with the new parser, it definitely isn't ready for prime time yet. And, neither the old nor the new parser have real overload resolution or (partial) template specialization. So, again, the answer to your question above depends on what kind of support you expect. May be we could break down the task into distinct chunks (parsing, analysis, etc.), to be able to estimate the efford and prioritize a bit. Thanks, Stefan