Hi,
I have been using Greg's racket mode and racket on the command line to
start my application. One of the most frustrating/infuriating things
about full time racket programming at the moment is debugging.
For example, here's a run of my program:
$ racket /var/tmp/lt15198411601519841160715/0/driver-0.rkt
<: contract violation
expected: real?
given: #f
argument position: 2nd
other arguments...:
1
context...:
/home/pmatos/Projects/lt/lt/stochastic.rkt:179:26
/var/tmp/lt15198411601519841160715/0/driver-0.rkt: [running body]
The context is quite unhelpful. Like 179 of stochastic.rkt is:
(lambda (candidate)
There's no call to '<' anywhere nearby.
DrRacket is not that much more helpful. If it helps, I currently setup
my project as:
raco pkg install --auto --link
raco setup --tidy --check-pkg-deps --unused-pkg-deps --pkgs lt
Is there anything I can try to improve backtrace generation?
Kind regards,
--
Paulo Matos
--
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.
