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

[Matthew Fluet]

> > > 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.
> 
> No, I meant leave the implementation of MLton.Exn.history the same:

Not that I felel that strongly about it.  I was just remarking that I
thought it could be done because the functional version of the history
list makes it much more transparent when it is and isn't being used.



-------------------------------------------------------
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