50 minutes ago, Daniel Bastos wrote:
>
> Say I have some application running. I told the shell
>
> ./run_my_application &
>
> Now, while using it, I notice a bug somewhere. How do I change the
> code and see its new effect without shutting down and rerunning the
> application?
Here's an ev
Jay's answer is in principle correct but you can get close to what Graham did
with a simple bit of planning.
Instead of a web application, let's start with an interactive application:
(define MY-PI 3)
(define (area-of-circle r)
(* MY-PI r r))
(define (repl)
(with-handlers ((exn? (lambda
Racket does not generally support this scenario. You could get close by doing...
% racket
> (require "myapp.rkt")
> (run)
> (set-box! some-function-called-by-app (lambda (...) new implementation))
But it would be very inconvenient to box all functions you may want to
change and you'd have to reme
Here's a quote from Paul Graham --- quoting from
http://bc.tech.coop/blog/040223.html.
"When one of the customer support people came to me with a report of a
bug in the editor, I would load the code into the Lisp interpreter and
log into the users' account. If I was able to reproduce the bug I'd
g
4 matches
Mail list logo
