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

[Stephen Weeks]

> Cool.  I also looked at exnHistory.sml.  If you remove the reference to
> SMLofNJ.exnHistory e and replace it with [exnName e], then one of the
> removeUnused pass will happily eliminate the history component from the
> raised exception.  Since the top-level handler looks at the history, the
> later exceptions (raised by the printing functions, etc.) do need to carry
> the history.

Neat.

> I suspect we could get away with always having implement-exceptions.fun
> rewrite as if exn-history were true.  Then -exn-history would only affect
> the behaviour of MLton.Exn.history.  When it was false, nothing could
> access the history component and it would be eliminated.

I wouldn't want to do this because people might want to use
MLton.Exn.history in their programs, but not always 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