racket/collects/errortrace
Matthew Flatt 9e7548de61 new error message convention
Add `raise-argument-error', `raise-result-error', `raise-arguments-error',
and `raise-range-error'.

The old convention was designed for reporting on a single (sometimes very
long line). The new convention is

 <name>: <short message>
   <field>: <detail>
   ...

If <detail> is long or itself spans multiple lines, then it may
also use the form

   <field>:
    <detail>

where each line of <detail> is indented by 3 spaces.

Backtrace information is shown as a multi-line "context" field.
2012-05-25 15:08:05 -06:00
..
lang first cut at submodules 2012-03-09 10:34:56 -07:00
private fix errortrace (required API changes), add `syntax-shift-phase-level' 2011-09-13 21:04:10 -06:00
scribblings errortrace: skip annotation in namespace with wrong base phase 2012-02-09 17:58:28 -07:00
errortrace-key.rkt rename all files .ss -> .rkt 2010-04-27 16:50:15 -06:00
errortrace-lib.rkt new error message convention 2012-05-25 15:08:05 -06:00
errortrace.rkt Switch to racket/base, and other racketizations. 2010-10-05 09:18:46 -04:00
main.rkt Switch to racket/base, and other racketizations. 2010-10-05 09:18:46 -04:00
stacktrace.rkt fix errortrace for submodules 2012-03-09 10:34:56 -07:00
zo-compile.rkt Switch to racket/base, and other racketizations. 2010-10-05 09:18:46 -04:00