Re: [CEDET-devel] Cogre - diagrams generated for eieio classes do not contain methods
Brought to you by:
zappo
From: Tomasz G. <to...@wp...> - 2013-01-04 21:12:31
|
"Eric M. Ludlam" <er...@si...> writes: > On 01/01/2013 06:42 PM, Tomasz Gajewski wrote: >> >> To better understand api of ede I wanted to check api for classes. As >> the documentation seems to not be fully accurate (details later) I >> wanted to check how cogre works for those classes. At first it seemed >> to be working fully as expected (it is really awesome) but there was >> no methods on the diagram. I've checked in the cogre code and it >> seems that there is support for externally defined methods (just like >> in eieio) but it doesn't work. I failed to find out why. I don't know >> enough to debug this. >> >> I wanted to describe it in more details but later I've found out that >> sample diagram on http://cedet.sourceforge.net/uml.shtml is based on >> eieio classes and doesn't have methods either. >> >> Is it supposed to work? > > Ah, yes. Externally defined methods. There used to be a subsystem in > semantic that crunched your entire project for all the classes and > methods, and merged them into a huge table. > > It kept breaking as other things evolved, and was eventually scrapped > as being out of model with Semantic as it had evolved. It was never > replaced. It seems it could be useful. Maybe some I'll ask questions about that as I would like to see much funcionality to be build around project but I'm not ready yet. > Cogre does use newer search functions to find external members on a > per class basis (semantic-tag-external-member-children), so that > should work. I looked into it and it seems that the default buffer > is the cogre buffer, and there are not semanticdb tables to search for > there. I checked in a small patch to make it search from the right > files, and to also do a brutish search, not an include based search. > It's a little slower now though. ;) Thanks. It works now. I have one more problem with this function on my c++ code (it doesn't find subclasses). If I fail to diagnose it I'll try to prepare some testcase. >> As about documentation I mention this only to help you fix it if you >> have time, not to blame. >> >> I started at 'ede-project-placeholder' and it took me quite some time >> to find out that 'ede–project-inode' does not exist but >> 'ede–-project-inode' does. And that '--' is replaced by texinfo into >> one 'en dash'. I couldn't find a way to workaround this >> replacement. Maybe it is a bug in @deffn? > > Interesting. Probably needs some sort of quote notation. > > That doc is auto-generated, so if quoting is needed, it shouldn't be > too bad. Hmmm. Actually that function has been commented out. I'll > have to find out why. This auto generation is only semi automatic, isn't it? ede.texi is normally versioned, not built. Is there a target to update it or some parts have to be replaced manually with generated content? >> And AFAIU all those :AFTER keywords are wrong. > > Thanks for the info. I don't know where those :AFTER keywords came > from. 'eieiodoc-one-node' seems to generate it. If I manage to understand why it generates wrong values I'll let you know. Regards Tomasz Gajewski |