> > > Pyret was a pain. Error messages were not clear and the whole change >> confused students. >> > > Can you elaborate more on this? My personal experience with Pyret is that > it has an exceptionally good error message, except when an internal > error occurs (which should not happen). >
IMO, Pyret's *parse* errors are terrible. To some extent they are an unavoidable consequence of infix, but it doesn't matter: parse errors just suck, even for me, even today, even as one of the three longest-running Pyret programmers. The run-time errors are (again IMO) much better than Racket's. Chris, FYI, Bootstrap:Reactive *was* in Racket to begin with, so there may not have been a need to "convert" it… Shriram -- 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/CAJUf2ySks8FFn6X9vuce_61dsnO6JbmGQetJXQ3ATGv5V5imjA%40mail.gmail.com.
