On 11/1/2020 4:45 PM, Robby Findler wrote:
It is true that running just "racket x.rkt" will not notice some situations where your .zo files are wrong and thus lead to the bad behavior George describes below but I find it quite handy to use .zo files during development, as they can speed things up considerably depending on what's happening in your application. If you are working at the command line and using something like "racket x.rkt" to run your program, then changing to "raco make x.rkt && racket x.rkt" will keep your .zo files all sync'd up.
Dunno ... too many times debugging in DrRacket I've run into situations where having .zo files screwed up tracing calls across modules in different source files.
In Racket's defense, I will say I haven't tried to do it with any recent versions ... my machines have always been fast, and (other than for performance testing or deployments) I gave up on caching .zo files a long time ago.
George -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/a5b8d35c-c21b-4f87-208d-98aa12174a34%40comcast.net.
