On 05/25/2015 11:16 AM, Greg Hendershott wrote: > Should there maybe be a parameter to control whether exn->string > returns anything interesting? And, should it be #f by default?
That's an interesting idea. I know of examples where Racket error reports have disclosed sensitive information. Such mistakes can be extremely subtle and difficult to anticipate, and even skilled, experienced engineers make them. Perhaps, if a parameter is a good idea (I'm not sure it is), when it is #f, exn->string could yield an instructive message such as "#<error redacted to avoid accidental information leak; see documentation for current-exn->string-enabled?>" plus suitable RED FONT DANGER TEXT in the documentation making it clear to users that they should think about the contexts in which the resulting strings will be published. Tony -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
