On Mon, Aug 26, 2013 at 11:19 PM, Bennie Kloosteman <[email protected]>wrote:
> But assuming you *do* want that, you still don't need to *copy* the stack >> frame. What you need to do is *preserve* the stack frames. As long as >> the stack frame is preserved, you can produce a pretty string later if you >> find that you need it. >> > > Which requires the runtime to gurantee that the adress to lookup is valid . > Sure. But if it isn't, you can't present a stack trace in *either* approach. > >>>> In more realistic code, argument validation failures would be handled >> as fatal errors, because they indicate a structural problem in the program. >> And we really shouldn't worry about a small marginal cost in what amounts >> to an exit() call. >> >> > Think GUI or validate html strings.. in a loop . > Validating html strings is input validation, not argument validation. Different problems => different idioms. > ... You cant have expected excepetion type on an interface .. > As I've said before: that's been tried, and it was a horrible practical failure. Be careful what you wish for. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
