On Mon, Feb 4, 2019 at 8:34 AM Laurent <laurent.ors...@gmail.com> wrote: > On Sun, Feb 3, 2019 at 7:00 PM Robby Findler <ro...@eecs.northwestern.edu> > wrote: >> On Sun, Feb 3, 2019 at 11:50 AM Laurent <laurent.ors...@gmail.com> wrote: >>> >>> I've pushed a repair. It should be integrated with the next racket nightly >>> release I suppose. >>> >>> The fix is to check the compiled version of all scripts in the library, and >>> if it differs from the current racket version it gets recompiled. The bonus >>> is that scripts that have not been compiled yet will now be, which means >>> faster loading time when triggering them. >>> >>> The caveat is that dependencies are not recompiled. This means that if a >>> script depends on a package/collection that hasn't been migrated/updated >>> yet, an error may be displayed on DrRacket startup (but appart from this >>> script DrRacket should still work fine). >> >> >> Can this error be caught and captioned with a better message or, even >> better, perhaps be integrated somehow into quickscript? (Maybe putting >> something into the menu or some other place somehow?) > > > Possibly. I'm not sure what would be the best option yet, I'll think about it > but I welcome suggestions.
I think the main thing should be to avoid any uncaught exceptions (if they happen while quickscript starts up, it will get disabled; if they happen later, they'll be labelled "internal error"s). How exactly to save the information and show it to the user in a nice way seems like there are lots of things to try out! Robby -- 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.
