[MLton-devel] cvs commit: -exn-history reimplemted

[Stephen Weeks]

> No, MLton.Exn.history is always used in the top-level handler.  Even when
> the user program doesn't use it explicitly.

Agreed.

> I agree that Mton.Exn.history should be like Assert.assert -- it should be
> a "nop" when -exn-history false is used.  I think it's arguable whether or
> not the top-level handler should print the exn history.  Certainly, it
> would be painful to wrap ever top-level evaluation with a handler if the
> user wants that information.  On the other hand, it seems like overkill to
> add another option that determines this behaviour.  Particularly since the
> reason someone compiles with -exn-history true is likely because they are
> trying to track down some uncaught exception. ;)

So I think we agree that the current way is best -- the top level
handler prints the history, and people turn it on when they want it
and are willing to incur the cost.


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel