3 ms·
> Just run the code in the debugger. How do you set a breakpoint on an annotation? You can’t, and that’s the issue. You can’t reason about annotations in the p
by layer8 3y ago
> Just run the code in the debugger.
How do you set a breakpoint on an annotation? You can’t, and that’s the issue. You can’t reason about annotations in the precise way you can reason about library calls.
- alex_smart 3y ago> How do you set a breakpoint on an annotation? You can’t, and that’s the issue. You can set a breakpoint on your normal method and you can see if any proxy object was introduced by the annotation in the call stack and set a breakpoint there. You can also just see the usages of the annotation to see where and how it is being used and set a breakpoint there. Anyway, going back to my original question, similar criticism is equally valid when you do metaprogramming in lisp/python/ruby. Why are these concerns only raised in the context of Java?