On 03/22/2011 03:02 AM, Darren Hoo wrote:
> eieio has support for documentation so that describe-variable or
> describe-function can be used on class definition and method definition
> , but where they are defined are not trackered, so directcly jumping from
> the from the help cross ref to the file position they are defined is
> impossible. I am really missing this feature.
> load-history only records defun, defface and defvar, but not defclass or
> defmethod..., so if these info is to be trackered, it should be done by
> eieio itself. I wonder if this can be improved.
> also if the question above is resolved, I think edebug on defmethod is then
> possible, ie, the real method of a generic can be decided at runtime and
> be instrumented by edebug whereby I can step into using keybing i in
> edebug, currently if I try to step into a method invocation, edebug just
> complains that it does not know where the function is defined.
I tried fixing that some years back. It is also related to
'unload-library" which is broken with any eieio based program. I was
not able to figure things out from that side (adding items to the load
history). I looked into augmenting aspects of find-function. That
works ok with mode-local, but at the time I didn't get it working w/
eieio classes. After all, which method of many do you want to jump to?
I don't doubt it is a solvable problem since eieio generates the help
text of all methods, so it could create links to the ones that match. I
think that's a matter of time for someone to tuck in and do it.
As for edebug, I use edebug with eieio a lot, and it works fine for
me. Perhaps there is a particular method you ran into that is
problematic that will reproduce this problem for someone on the mailing