As a two-time debugger author, I guess I don't really see any particular benefit to reflection for debugging support. What I'm probably not taking into account is the need to debug dynamically generated code. It isn't clear to me how important dynamically generating code from the program is in real life. I wonder if it isn't a case of one kind of dynamic usage begetting another. I need to understand the pros and cons of that more clearly.
Outside of dumps for bug reports, which are initiated by the runtime and need not be program accessible, I'm pretty convinced that reflection on stack frames is a really bad idea. At minimum it's a violation of encapsulation. I'm *definitely* not sold on reflection for pretty-printing. The compiler can generate that at compile time in a user-overridable way. But it's possible that I'm just being a luddite here. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
