i'm trying to find good examples of something that... might not exist.
i want to document my code at the definition of each new form, similar to, say,
javadoc. i'd rather not write a separate document. i looked for examples in
the racket 6.5 sources. "syntax/parse/private/litconv.rkt" taught
On Wednesday, May 18, 2016 at 8:41:50 PM UTC-4, Robby Findler wrote:
> I've pushed a fix for this.
thanks so much!
> ... It also makes the more
> standard stacktraces better too, but may not help you much in this
> case if you don't use errortrace (or DrRacket).
do i need to enable errortrace in
i made a one-character typo that created an error without a relevant line
number. when applying a (listof predicate) in my struct's contract, i
accidentally supplied a non-predicate function -- which is very easy to do when
the predicate is the name of a struct. (i forgot the question mark.)
On Sunday, May 15, 2016 at 10:26:41 PM UTC-4, Braids Constance wrote:
> second, i'd like to see DrRacket display the value of the most recently
> evaluated expression.
after reading about expression level breakpoints in DrRacket, i now see that it
displays this information in the t
hello, i tried using the DrRacket debugger for the first time yesterday. it
was a bit frustrating, because i couldn't figure out how to set a line-level
breakpoint. leif later told me i can set a breakpoint on an expression, but
not a line. that's smart, surely, but not what i'm used to.
sec
5 matches
Mail list logo
