>And most of all, does the tool *try* to build a calling sequence from the code to get a better picture of privates already in use ? Should be the most demanding part, but as the calling hierarchy could be displayed back in FP days, not insurmountable <g>.

Yes, the Snap! tool, which then got rewritten in Fox itself (the Doc wizard, as it was named later) - but it goes through your whole project, and surely can't guess calls via name expressions and macros - and we'd have to add bindevent() calls to that, just to make things more interesting. And, yes, .method() calls in with/endwith blocks where the object is a local reference to our class addobject()ed to a container object. I'd like to see that AI which can catch that :).

Getting spoiled, aren't we? :)