On Wednesday, March 2, 2011 at 5:53:50 PM UTC, Jay McCarthy wrote: > The unstable/debug library That's nice, I suppose, for standardizing the practice of sticking printf statements here and there for function results. It's basically what Matthias was saying, except with some additional forms for automatically wrapping `debug` around definitions and stuff. Might be more useful if begin/debug didn't introduce an expression context.
> I also put my own custom > information in continuation marks and extract it later to learn more > about the context. NB. My mark parameter library provides a nice layer > atop cmarks for this: > > http://docs.racket-lang.org/unstable/Mark_Parameters.html This, I'm curious about. So all you're doing is like: (parameterize ((context 'top)) ... (parameterize ((context 'deeper)) ... (parameterize ((context 'deep)) ...) ...) ...) and then upon error, examine (context) to see what its value ends up being? How are 'continuation marks' different from regular parameters, and superior for this sort of thing? -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
