suzanne.soy/scribble-enhanced
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

- Newline strings instead of `eol' identifiers

Browse Source 
- Special text markers are |{ ... }|
- No more need for $ escapes, use body-less @-commands
- Add indentation strings

svn: r2969

original commit: 4f6b53c1d0b055792ba36d82723c3aaf8eb36ce7
This commit is contained in:
Eli Barzilay 2006-05-18 18:32:13 +00:00
parent 63a69a4844
commit a065dfaf7f
1 changed files with 165 additions and 68 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

233
collects/scribble/doc.txt
View File

@ -1,40 +1,49 @@
Implements the @-reader macro for embedding text in Scheme code. The _Scribble_ Collection
=========================
The Scribble collection is a few libraries that can be used to create
documents from Scheme. It is made of independently usable parts. For
example, the reader can be used in any situation that requires lots of
free-form text, or you can use the rendering portion directly to
generate documents.
The Scribble Reader
------------------
*** Introduction *** Introduction
The @-reader is designed to be a convenient facility for embedding The @-reader is designed to be a convenient facility for using free-form
Scheme code and text. "@" is chosen as one of the least-used characters text in Scheme code. "@" is chosen as one of the least-used characters
in Scheme code (the options are: "&" (969 uses in the collects in Scheme code (the options are: "&" (969 uses in the collects
hierarchy), "|" (1676), "@" (2105) "^" (2257) "$" (2259)). hierarchy), "|" (1676), "@" (2105) "^" (2257) "$" (2259)).
To use this file, you can use MzScheme's #reader form: To use this file, you can use MzScheme's #reader form:
#reader(file "...path to this file...") #reader(lib "reader.ss" "scribble")
But note that this will only do the concrete-level translation, and not but note that this will only do the concrete-level translation, and not
give you any useful bindings. Alternatively, you can start MzScheme, give you any useful bindings. Alternatively, you can start MzScheme and
require this file and use the `use-at-readtable' function to switch the use the `use-at-readtable' function to switch the current readtable to
current readtable to the at-readtable. You can do this in a single the at-readtable. You can do this in a single command line:
command line:
mzscheme -te ...this-file... '(use-at-readtable)' mzscheme -Le reader.ss scribble "(use-at-readtable)"
*** Concrete Syntax *** Concrete Syntax
The *concrete* syntax of @-commands is (informally, more details below): The *concrete* syntax of @-commands is (informally, more details below):
"@" <cmd> "[" <key-vals> "]" "{" <body> "}" "@" <cmd> "[" <key-val> ... "]" "{" <body> ... "}"
where all parts are optional, but at least one should be present. where all parts are optional, but at least one should be present.
(Note: since the reader will try to see if there is a "{...body...}" in (Note: since the reader will try to see if there is a "{...body...}" in
the input, it is awkward to use body-less constructs on an interactive the input, it can be awkward to use body-less constructs on an
REPL since reading an expression succeeds only when there is a new interactive REPL since reading an expression succeeds only when there is
expression available.) "@" is set as a terminating reader macro, so if a new expression available.) "@" is set as a terminating reader macro,
you want to use it in Scheme code, you need to quote it with `\@' or the so if you want to use it in Scheme code, you need to quote it with `\@'
whole identifier with `|ba@rs|'. This has no effect occurrences of "@" or the whole identifier with `|ba@rs|'. All of this has no effect
in Scheme strings. on occurrences of "@" in Scheme strings, character constants etc.
Roughly speaking, such a construct is translated to: Roughly speaking, such a construct is read as:
(<cmd> <key-val> ... <body> ...) (<cmd> <key-val> ... <body> ...)
@ -48,8 +57,8 @@ string for each end of line. For example:
blah} blah}
It is your responsibility to make sure that `foo' is bound (in any way: It is your responsibility to make sure that `foo' is bound (in any way:
it can be a macro). To see the forms, you can use quote as usual, for it can be either a function or a macro). To see the forms, you can use
example: quote as usual, for example:
'@foo{bar} '@foo{bar}
@ -61,8 +70,9 @@ wrapping the *whole* expression. For example:
@`',@foo{blah} --is-read-as--> `',@(foo "blah") @`',@foo{blah} --is-read-as--> `',@(foo "blah")
When writing Scheme code, this means that @`',@foo{blah} is exactly the When writing Scheme code, this means that @`',@foo{blah} is exactly the
same as `@',@foo{blah} and `',@@foo{blah}, but these constructs can same as `@',@foo{blah} and `',@@foo{blah}, but unlike the latter two,
appear in body texts where they will be read differently (see below). the first construct can appear in body texts with the same meaning,
whereas the other two would not work (see below).
The command itself is not limited to a Scheme identifier -- it can be The command itself is not limited to a Scheme identifier -- it can be
any Scheme expression: any Scheme expression:
@ -76,15 +86,16 @@ just strings:
@{foo bar --is-read-as--> ("foo bar" "\n" "baz") @{foo bar --is-read-as--> ("foo bar" "\n" "baz")
baz} baz}
@'{foo bar --is-read-as--> (quote ("foo bar" "\n" "baz")) @'{foo bar --is-read-as--> '("foo bar" "\n" "baz")
baz} baz}
If the command part begins with a ";" (with no newline between the "@" If the command part begins with a ";" (with no newline between the "@"
and the ";"), then the construct is a comment. There are two comment and the ";"), then the construct is a comment. There are two comment
forms, one for an arbitrary-text, possibly nested comments, and another forms, one for arbitrary-text and possibly nested comments, and another
one for a -to-the-end-of-the-line comment: one for a -to-the-end-of-the-line comment:
@; <any-space>* { ...any-text-including-newlines... } @; <any-space>* { ...any-text-including-newlines... }
@; <anything-that-doesn't-begin-with-a-brace-to-the-end-of-the-line> @; <anything-that-doesn't-begin-with-a-brace-to-the-end-of-the-line>
Note that in the first form the commented body must still parse Note that in the first form the commented body must still parse
@ -107,28 +118,38 @@ or
otherwise you will probably confuse the editor into treating the file as otherwise you will probably confuse the editor into treating the file as
having imbalanced parenthesis. having imbalanced parenthesis.
If only the command part is specified, then the result is the command
part only, without an extra set of parenthesis. This makes it suitable
for Scheme escapes in body texts. More below, in the description of the
body part.
Finally, note that there are no special rules for using "@" in the Finally, note that there are no special rules for using "@" in the
command itself, which can lead to things like: command itself, which can lead to things like:
@@foo{bar}{baz} --is-read-as--> ((foo "bar") "baz") @@foo{bar}{baz} --is-read-as--> ((foo "bar") "baz")
but you should *not* rely on such behavior, since "@@" might be used but you should not rely on such behavior, since "@@" might be used
differently in the future (eg, making "@@" be "@" in a body text). differently in the future (eg, making "@@" be "@" in a body text).
** Concrete Syntax: the body part ** Concrete Syntax: the body part
The syntax of the body part is intended to be as convenient as possible The syntax of the body part is intended to be as convenient as possible
for writing free text. It can contain free text, and the only for writing free text. It can contain almost any text -- the only
characters with special meaning are braces, "@", "$", "|". As described character with special meaning is "@", in addition, braces, "|", and
above, the text turns to string arguments for the resulting forms. backslash can have special meanings but only in a few contexts. As
Spaces at the beginning of lines are discarded, and newlines turn to described above, the text turns to a sequence of string arguments for
"\n" strings. As part of trying to do the `right thing', an empty line the resulting form. Spaces at the beginning of lines are discarded (but
at the beginning and at the end are discarded, so see the information about indentation below), and newlines turn to
individual "\n" strings. (Spcaces are preserved on a single-line text.)
As part of trying to do the `right thing', an empty line at the
beginning and at the end are discarded, so
@foo{ @foo{
bar --is-read-as--> (foo "bar") <--is-read-as-- @foo{bar} bar --is-read-as--> (foo "bar") <--is-read-as-- @foo{bar}
} }
@foo{ bar } --is-read-as--> (foo " bar ")
If an "@" appears in the input, then it is interpreted as Scheme code, If an "@" appears in the input, then it is interpreted as Scheme code,
which means that the at-reader will be applied recursively, and the which means that the at-reader will be applied recursively, and the
resulting syntax will appear as an argument, among other string resulting syntax will appear as an argument, among other string
@ -136,14 +157,36 @@ contents. For example:
@foo{a @bar{b} c} --is-read-as--> (foo "a " (bar "b") " c") @foo{a @bar{b} c} --is-read-as--> (foo "a " (bar "b") " c")
A "$" also switches to Scheme mode, but it is a simple escape back to If the nested "@" construct has only a command -- no body part, then it
Scheme: it will read the next Scheme expression and plant it in the does not appear in a subform. Given that the command part can be any
form. The expression can be wrapped in braces in case it touches text Scheme expression, this makes "@" a general escape to arbitrary Scheme
that you don't want to include. Examples code:
@foo{foo $bar foo} --is-read-as--> (foo "foo " bar " foo") @foo{a @bar c} --is-read-as--> (foo "a " bar " c")
@foo{foo$bar.} --is-read-as--> (foo "foo" bar.)
@foo{foo${bar}.} --is-read-as--> (foo "foo" bar ".") @foo{a @(bar 2) c} --is-read-as--> (foo "a " (bar 2) " c")
In some cases, you may want to use a Scheme identifier (or a number or a
boolean) in a position that touches other text that can make an
identifier -- in these situations you should surround the Scheme
identifier (/number/boolean) by a pair of bar characters. The text
inside the bars is parsed as a Scheme expression, but if that fails, it
is used as a quoted identifier -- do not rely on this behavior, and
avoid using whitespace inside the bars. Also, if bars are used, then no
body text is used even if they are followed by braces (see the next
paragraph). Examples:
@foo{foo @bar foo} --is-read-as--> (foo "foo " bar " foo")
@foo{foo@bar.} --is-read-as--> (foo "foo" bar.)
@foo{foo@|bar|.} --is-read-as--> (foo "foo" bar ".")
@foo{foo@3.} --is-read-as--> (foo "foo" 3.0)
@foo{foo@|3|.} --is-read-as--> (foo "foo" 3 ".")
@foo{foo@|(f 1)|{bar}.} --is-read-as--> (foo "foo" (f 1) "{bar}.")
Braces are only problematic because a "}" is used to mark the end of the Braces are only problematic because a "}" is used to mark the end of the
text. They are therefore allowed, as long as they are balanced. For text. They are therefore allowed, as long as they are balanced. For
@ -152,15 +195,83 @@ example:
@foo{f{o}o} --is-read-as--> (foo "f{o}o") @foo{f{o}o} --is-read-as--> (foo "f{o}o")
There is also an alternative syntax for the body, one that specifies a There is also an alternative syntax for the body, one that specifies a
new marker for the end. To do this, use two openning braces with new marker for the end. To do this, use "|{" for the openning marker,
punctuation characters between them (no spaces, and no alphanumerics). optionally with additional characters between them (excluding "{",
If this form is used, then the reversed form (reverse the charcters and whitespace, and alphanumerics) -- the matching closing marker should be
swap round, square, curly, and angle parentheses) is used to close the the mirrored form of the openning marker (reverse the characters and
text. For example: swap round, square, curly, and angle parentheses). For example:
@foo{<{foo{{{bar}>} --is-read-as--> (foo "foo{{{bar") @foo|{...}| --is-read-as--> (foo "...")
For situations where spaces at the beinning of lines matter (various @foo|{foo{{{bar}| --is-read-as--> (foo "foo{{{bar")
@foo|<{{foo{{{bar}}>| --is-read-as--> (foo "{foo{{{bar}")
* Concrete Syntax: quoting in body texts
To quote braces or "@", precede them with a backslash. Note that this
is an irregular use of backslash quoting! To use "\@" in your text,
simply precede it with a backslash. The general rule is that to use N
backslashes-and-a-special-character, you should precede it with one
extra backslash. Any other use of a backslash (one that is not followed
by more back-slashes and a special character) is preserved in the text
as usual. Examples:
@foo{b\@ar} --is-read-as--> (foo "b@ar")
@foo{b\\@ar} --is-read-as--> (foo "b\\@ar")
@foo{b\\\@ar} --is-read-as--> (foo "b\\\\@ar")
@foo{b\{\@\@ar} --is-read-as--> (foo "b{@@ar")
@foo{b\ar} --is-read-as--> (foo "b\\ar")
@foo{b\\ar} --is-read-as--> (foo "b\\\\ar")
* Concrete Syntax: newlines and indentation
When indentation is used, all-space indentation string syntaxes are
perpended to the beginning of each line. The rule for adding these
string is:
- A spaces-string is added to each line according to its distance from
the leftmost syntax object;
- The first string is not prepended with indentation if it appears on
the first line of output.
Examples:
@foo{ --is-read-as--> (foo "bar" "\n"
bar " " "baz" "\n"
baz "bbb")
bbb}
@foo{bar --is-read-as--> (foo "bar" "\n"
baz " " "baz" "\n"
bbb} "bbb")
@foo{ bar --is-read-as--> (foo " bar" "\n"
baz " " "baz" "\n"
bbb} " " "bbb")
@foo{bar --is-read-as--> (foo "bar" "\n"
baz "baz" "\n"
bbb} "bbb")
@foo{ bar --is-read-as--> (foo " bar" "\n"
baz "baz" "\n"
bbb} "bbb")
@foo{ bar --is-read-as--> (foo " bar" "\n"
baz "baz" "\n"
bbb} " " "bbb")
Additional notes:
- You can identify indentation strings at the syntax level by the fact
that they have the same location information as the following syntax
object;
- This mechanism depends on line and column number information
(`use-at-readtable' turns them on for the current input port);
- When using it on a command-line, you note that the reader is not aware
of the "> " prompt, which might lead to confusing results.
[The following is likely to change.]
For situations where spaces at the beginning of lines matter (various
verbatim environments), you should begin a line with a "|". It has no verbatim environments), you should begin a line with a "|". It has no
other special meaning -- so to use a "|" as the first character in the other special meaning -- so to use a "|" as the first character in the
text, simply use another before it. text, simply use another before it.
@ -173,7 +284,7 @@ text, simply use another before it.
In other situations, newlines matter -- you might want to avoid a In other situations, newlines matter -- you might want to avoid a
newline token in some place. To avoid a newline and still break the newline token in some place. To avoid a newline and still break the
source line, use a line comment. As in TeX, these will consume text source line, use a line comment. As in TeX, these will consume text
upto and including the end of the line and all following whitespace. up-to and including the end of the line and all following whitespace.
Example: Example:
@foo{bar @; @foo{bar @;
@ -187,32 +298,18 @@ text:
baz@; --is-read-as--> (foo "bar baz .") baz@; --is-read-as--> (foo "bar baz .")
| .} | .}
Finally, to quote braces, "@" or "$", precede them with a backslash.
Note that this is an irregular use of backslash quoting! To use "\@" in
your text, simply precede it with a backslash. The general rule is that
to use N backslashes-and-a-special-character, you should precede it with
one extra backslash. Any other use of a backslash (one that is not
followed by more bslashes and a special character) is preserved in the
text as usual. Examples:
@foo{b\$ar} --is-read-as--> (foo "b$ar")
@foo{b\\$ar} --is-read-as--> (foo "b\\$ar")
@foo{b\\\$ar} --is-read-as--> (foo "b\\\\$ar")
@foo{b\{\$\@ar} --is-read-as--> (foo "b{$@ar")
@foo{b\ar} --is-read-as--> (foo "b\\ar")
@foo{b\\ar} --is-read-as--> (foo "b\\\\ar")
** Concrete Syntax: the keyword-value part ** Concrete Syntax: the keyword-value part
The keyword-value part can contain arbitrary Scheme expressions, which The keyword-value part can contain arbitrary Scheme expressions, which
are simply stacked before the body text: are simply stacked before the body text arguments:
@foo[1 (* 2 3)]{bar} --is-read-as--> (foo 1 (* 2 3) "bar") @foo[1 (* 2 3)]{bar} --is-read-as--> (foo 1 (* 2 3) "bar")
@foo[@bar{...}]{blah} --is-read-as--> (foo (bar "...") "blah")
But there is one change that makes it easy to use for keyword/values: But there is one change that makes it easy to use for keyword/values:
first of all, "=" is a terminating character in the textual scope. (a) "=" is a terminating character in the textual scope, (b) if there is
Secondly, if there is a "<identifier>=<expr>" sequence (spaces a "<identifier>=<expr>" sequence (spaces optional), then it is converted
optional), then it is converted to "#:identifier <expr>": to "#:identifier <expr>":
@foo[(* 2 3) a=b]{bar} --is-read-as--> (foo (* 2 3) #:a b "bar") @foo[(* 2 3) a=b]{bar} --is-read-as--> (foo (* 2 3) #:a b "bar")
@ -222,7 +319,7 @@ This facility can be used in any way you want. All you need is to use
function names that you bind. You can even use quasi-quotes, skipping function names that you bind. You can even use quasi-quotes, skipping
the need for functions, for example: the need for functions, for example:
> (define (important . text) @`b{@u{@big{$,@text}}}) > (define (important . text) @`b{@u{@big{@,@text}}})
> (important @`p{This is an important announcement! > (important @`p{This is an important announcement!
Read it!}) Read it!})
(b (u (big (p "This is an important announcement!" eol "Read it!")))) (b (u (big (p "This is an important announcement!" "\n" "Read it!"))))