I started from tabs that are not on the beginning of lines, and in
several places I did further cleanings.
If you're worried about knowing who wrote some code, for example, if you
get to this commit in "git blame", then note that you can use the "-w"
flag in many git commands to ignore whitespaces. For example, to see
per-line authors, use "git blame -w <file>". Another example: to see
the (*much* smaller) non-whitespace changes in this (or any other)
commit, use "git log -p -w -1 <sha1>".
original commit: 672910f27b856549ad08d38832b6714edf226c8e
if there already was one that I didn't find). Also fixed syntax
error raising procedure.
closes PR 12859
original commit: c0b928c758cc64b7b902fbe38838d31a3c1bc008
Macros and other tools that need syntax privilege used
`(current-code-inspector)' at the module top-level to try to
capture the right code inspector at load time. It's more
consistent to instead use the enclosing module's declaration-time
inspector, and `var-ref->mod-decl-insp' provides that. The
new function works only on references to anonymous variables,
which limits access to the inspector.
The real function name is longer, of course.
original commit: 0197902309c5400d463393829a88282c627dafd2
Started as fixing misindented definitions, then more indentations, then
a bunch of similar things (square brackets, huge spaces at end-of-lines,
etc).
original commit: d61eb53686f735b979a60dc6f9efd3d2aa9777d9
added tutorial, racket categories
relabeled some other categories
normalized manual names: de-bolded, changed some names
original commit: 1b702a2ae32aba835f7467ced6b203902db0ccd9
Also, updates some of the mzlib files to point at `racket/*' libraries
rather than to `scheme/*' ones.
original commit: ac26fe75546b5182d78f18c2cd882f0f440849e2
punctuations outside of the form, as it does with quote punctuations.
So things like this
#, @foo{...}
that required the space to make the @foo read as a scribble form are
now better written as
@#,foo{...}
This changes all such occurrences. (In case you see this change in
your files and are worried that there might be changes: I mechanically
verified that the result of `read'ing the modified files is identical
to the previous version.)
svn: r15111
original commit: 4288c6c2c703664b6bbd4cd06bd7c2160985b00d
tree and verifying that there are no changes).
(Also fixed a few bugs that were in the code)
svn: r14427
original commit: c0a8a0122200209e38dff1959d79b58f847814db
Danny Yoo