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
file. (That is, it does not require the file to have a `name'
entry.)
* The name shown when setup works is the directory name, followed by
the `name' field from the info file when specified.
* This means that many `name's are no longer needed, so I'm removing
them. To see if you need a `name' entry, consider that the name
will be shown like this:
... foo (<your name here>)
This means that if the name is the same as the directory name, then
there is no point in having it. I also removed cases where the name
differed only in its capitalization for collections where the case
is obvious.
* Also, for subcollections, the name should clarify the name of the
subcollection in context. For example "Acknowledgments" explains
what scribbling/acks is, but there's no need to add the context name
as in "Scribblings: Acknowledgments".
* There may also be a point in keeping names for other uses. One such
example was in games, where the name field was used in the PLT Games
application. (This was changed to default on the directory name, so
it is no longer needed in most games.) Another example is in planet
packages.
svn: r8629
original commit: 699c40643d538e54164bf68f5eddf43ae30c5b5e
Matthew Flatt