IRC channel logs

2014-01-03.log

back to list of logs

<linas>hi tupi mark_weaver .. not using gnome
<linas>not setting port encoding, I thought I read that all ports are utf-8 by default ... and anyway, utf8 seems to work 99.99% of the time.
<linas>I do set (setlocale LC_ALL "")
<linas>I do get a stack trace, but its utterly uninformative ... its just ?: 3 [# # eval] or something like that
<linas>a few catch-closure and boot-9.scm for good measure.
<linas>But that's a raw stack dump, not a debugger stack dump, which might show more.
<linas>I've got to figure out how to invoke the debugger ... the problem is, this is all a multi-hour batch job
<linas>and if the error is caught, it prints, and moves on.
<nalaginrut>morning guilers~
<b4283>morning
<nalaginrut>heya
*davexunit found and fixed a bug in guile-wm :)
<mark_weaver>linas: make sure your scheme code is compiled. compiled code has much better debugging.
<mark_weaver>from your description of the backtrace, it sounds like the code is not compiled.
<linas>Hmm...
<civodul>Hello Guilers!
<ijp>hello
<civodul>happy new year and everything!
<civodul>it's the 2.2 year!
<dsmith-work>Happy Friday, Guilers!!
<dsmith-work>Whee! 2.2!
<civodul>hey dsmith-work
<davexunit>hey guilers
<ijp>"We saw in Part One that an interactive top-level loop necessarily violates referential transparency"
<ijp>that may sound like something written by one of the nice racket folks, but in fact, it is much much older
<civodul>ijp: reference?
<ijp>1978, steele and sussman
<civodul>oh!
<ijp>"The Art of the Interpreter, or, The Modularity Complex"
<ijp>aka. the lambda paper I had somehow not read before
<civodul>interesting
***mario-go` is now known as mario-goulart
<mark_weaver>sneek: seen wingo?
<sneek>wingo was here Dec 13 at 12:09 pm UTC, saying: that is a test of the stack :) test on loops and the difference is much more.