On Thu, Sep 02 2010, Robby Findler wrote:
> I think you probably want to use the errortrace library. That's what
> DrRacket uses (and how it gets the better error messages).
That's exactly what i was looking for. Thanks a lot, Robby.
jao
_
For l
I think you probably want to use the errortrace library. That's what
DrRacket uses (and how it gets the better error messages).
Robby
On Sun, Aug 29, 2010 at 6:04 PM, Jose A. Ortega Ruiz wrote:
>
> In Racket 5.0.1, with, say, f.rkt containing:
>
> #lang racket
> (provide bar)
> (define (fo
Yes, this is a a rough one. You know the error is out there ... somewhere ...
Another one is exception traces not printing with a writer output
stream is closed error. Reports correctly in DrRacket, its at the
command line the problem is visible. I'll create a reproducible case
later this eveni
In Racket 5.0.1, with, say, f.rkt containing:
#lang racket
(provide bar)
(define (foo x) x)
(define (bar) (foo))
requiring f.rkt at racket's textual REPL via `(require (file "f.rkt"))'
works fine (as expected) and calling `(bar)' gives an error (again as
expected); but the error mess
4 matches
Mail list logo
