This one[1] sounds so awesome! I just read the paper.
In particular I like how one could access the current call stack
structure live.
However, the most recent changes to the code are from early 2009.
Anyone knows what happened to this?
[1]
On Sun, Apr 7, 2013 at 12:23 AM, Steffen Schuldenzucker
sschuldenzuc...@uni-bonn.de wrote:
For the moment I think it would be enough to auto-insert the location of
calls to a certain set of functions.
Have you tried assert [1]?
[1]
Hi Steffen,
most of the time I'm just using these cpp macros:
#define __POS__(__FILE__ ++ : ++ show __LINE__)
#define ERROR error $ __POS__ ++ - ++
Instead of writing 'error blub' you would write 'ERROR blub'
and additionally get the file name and the line.
There's a bracktracing
Good Point!
Doesn't quite meet my requirements (I don't want to show the error loc
somewhere deep within the libs), but it led me here[1].
Reading through that now...
[1] http://hackage.haskell.org/trac/ghc/wiki/ExplicitCallStack
On 04/06/2013 07:51 PM, Kim-Ee Yeoh wrote:
On Sun, Apr 7,
On Sun, Apr 7, 2013 at 4:37 AM, Steffen Schuldenzucker
sschuldenzuc...@uni-bonn.de wrote:
Reading through that now...
[1] http://hackage.haskell.org/trac/ghc/wiki/ExplicitCallStack
If you're reading that page, you probably also want to get up to speed
on the latest. The thread titled RFC:
