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.
Robby On Sun, Nov 1, 2020 at 3:27 PM George Neuner <gneun...@comcast.net> wrote: > > On 11/1/2020 11:34 AM, infodeveloperdon wrote: > > so that when I run Racket it recreates the 'compiled' directories > > using the latest compiler. > > Or is there a better way? > > Yeah ... don't use 'compiled' directories for development - they can get > out of sync and screw up your debugging. > > They really are only useful for performance testing or for deployment in > situations where you don't want to (or can't) build a single executable. > > 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/b83b03b4-f2a8-2b6c-7ac8-00caa1e6d104%40comcast.net > . > -- 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/CAL3TdOPf70L21NT%2Bn4%2B62OHYQtRXJA1wP%2BTVE-HzjenjQsS1Tw%40mail.gmail.com.
