[MLton-devel] profiled self compile with source info

[Stephen Weeks]

> Maybe this has already occured to everyone else, but it only struck me
> yesterday.  Given the above and the labels that the native codegen will
> insert at the corresponding points, it should be almost trivial to
> generate debugging information.  

Yeah, the thought had occurred to me.

> It might be more difficult to set
> breakpoints; certainly for anonymous functions, there is no cannonical
> name with which to associate the break; even for named functions, lexical
> scoping would seem to make it easy to confuse names. 

I'd definitely go for setting break point by line number, not function
name.  After all, that's what we have with SourceInfo and that's
pretty canonical (up to duplicates anyway).

> Anyways, I definitely think that source level debugging even at just
> the control-flow level would be a great addition to MLton.

Agreed.


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel