The Racket repository
![]() for syntax errors (i.e., exn:fail:syntax? exceptions) Overall, it seems important to (in most cases) not show the stack that leads to the point where raise-syntax-error is called, so as not to confuse users who might think that that stack is useful information in understanding how to fix the syntax error. I've resisted this technique for avoiding those stacks for a long time, mostly because common syntax errors in the standard settings don't usually get the stacktrace button because they usually have empty stacks (partly thanks to the with-stack-checkpoint dance). But now that the underlying racket-generated stack is shown too, and not just the errortrace-generated stack, it is harder to make those go away. More precisely, DrRacket used to be able to rely on the fact that files that were compiled to .zo files would not have the instrumentation in them and thus stackframes from that code would not show up in the stacktrace. No longer. So, it seems time to try this alternative. |
||
---|---|---|
collects | ||
doc | ||
man/man1 | ||
src | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
README |
The Racket programming language =============================== Important executables: * DrRacket: Racket's integrated development environment (start here!). * Racket: the main command-line entry point for running racket programs and scripts. * GRacket: the GUI-mode Racket executable. * raco: Racket's command-line toolset. More Information ---------------- Racket comes with extensive documentation: use DrRacket's `Help' menu, or run `raco docs'. Also, visit us at http://racket-lang.org/ for more Racket resources. Instructions for building Racket from source are in src/README. License ------- Racket Copyright (c) 2010-2011 PLT Scheme Inc. Racket is distributed under the GNU Lesser General Public License (LGPL). This means that you can link Racket into proprietary applications, provided you follow the rules stated in the LGPL. You can also modify Racket; if you distribute a modified version, you must distribute it under the terms of the LGPL, which in particular means that you must release the source code for the modified software. See doc/release-notes/COPYING.txt for more information.