Re: Improved patch to jde-wiz.el (for deep inner-class names)
"Jeff Peck" <[email protected]>
| Newsgroups | gmane.emacs.jdee.devel |
|---|---|
| Message-ID | <80E84B54E80946BABBDC6AD7A0D87654@blue> |
Tell me more. You say there is a problem with "error handling", but what error is being handled? For me, with ZCat.java compiled and ZCat$FooBar.class on the class path, it works. The *first* time i tried your test, my prj.el had a wrong classpath, and bsh had been working on other projects, so FooBar was not found (but even then a single, simple message) but after clearing that, it works as expected. Looks like either the patch is incorrecly installed or your JDEE-bsh is confused about what is where...? That [1220 times] and "Variable binding depth exceeds max-specpdl-size" message looks like runaway recursion, signs of a bad patch... the real code could not do that [TTBOMK]. Maybe revert to 164 and try again? (patch attached) ----- Original Message ----- From: "Len Trigg" <[email protected]> To: "Jeff Peck" <[email protected]> Cc: <[email protected]> Sent: Tuesday, November 17, 2009 7:35 PM Subject: Re: [jdee-devel] Improved patch to jde-wiz.el (for deep inner-class names) > Jeff Peck wrote: >> Improved patch to jde-wiz.el, so implement-interface can find deeply >> nested class/interface. >> (recurse, replacing last '.' with '$' until class is found) > > Needs some improvement to error handling. I tried invoking > jde-wiz-implement-interface FooBar from within Blah in the following > small test file I had around. > > Before the patch: > > error : (error "Error: could not find interface named: ZCat.FooBar. Note: > name must be qualified.") [2 times] > error : (error "Error: could not find interface named: ZCat$FooBar. Note: > name must be qualified.") [2 times] > Error: could not find interface named: ZCat$FooBar. Note: name must be > qualified. > > > After the patch: > > error : (error "Error: could not find interface named: ZCat.FooBar. Note: > name must be qualified.") [2 times] > error : (error "Error: could not find interface named: ZCat$FooBar. Note: > name must be qualified.") [1220 times] > error in process filter: typep: Variable binding depth exceeds > max-specpdl-size > error in process filter: Variable binding depth exceeds max-specpdl-size > error : (error "Error: could not find interface named: ZCat$FooBar. Note: > name must be qualified.") [2 times] > error in process filter: byte-code: Variable binding depth exceeds > max-specpdl-size > error in process filter: Variable binding depth exceeds max-specpdl-size > error : (error "Error: could not find interface named: ZCat$FooBar. Note: > name must be qualified.") > error in process filter: apply: Variable binding depth exceeds > max-specpdl-size > error in process filter: Variable binding depth exceeds max-specpdl-size > error in process filter: timer--time-less-p: Variable binding depth > exceeds max-specpdl-size > error in process filter: Variable binding depth exceeds max-specpdl-size > error : (error "Error: could not find interface named: ZCat$FooBar. Note: > name must be qualified.") > error in process filter: typep: Variable binding depth exceeds > max-specpdl-size > error in process filter: Variable binding depth exceeds max-specpdl-size > error : (error "Error: could not find interface named: ZCat$FooBar. Note: > name must be qualified.") > error in process filter: eieio-validate-slot-value: Variable binding depth > exceeds max-specpdl-size > error in process filter: Variable binding depth exceeds max-specpdl-size > > And I get left at a minibuffer prompt "Lisp expression:" > > > Cheers, > Len. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july