1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
@Section
@Title { Embedding Lout commands within program comments }
@Tag { cpcomm }
@Begin
@PP
It is possible to embed Lout text inside program comments. How this
programs. @RawIndex { programs }
programs.loutcode @SubIndex { Lout code embedded in }
loutcode.programs @Index { Lout code embedded in programs }
is done could in principle vary from language to language, but in
every language supported so far it is done by starting off the comment
with an @Code "@" character. If the language has several ways to get
a comment, this will work every way. The entire comment after the @Code "@"
character should then be Lout text. For example, to force Lout to start
a new page at some point within a C program, place
@ID @Code "/*@ @NP */"
at that point. (In this case you can also simply include a formfeed
character without any comment; see Section {@NumberOf formfeed}
for more on this.) Or, to make a heading in an Eiffel program, do this:
@ID @Code "--@ @Display @Heading { treeprint }"
(Eiffel comments begin with @Code "--" and end at the end of the
line.) Other possible uses for this feature include index entries and
margin notes. Incredible as it may seem, you can even write
@ID @Code "/*@ @CD @Heading { Function @CP { treeprint() } } */"
with @Code "@CP" and C code inside the Lout code inside the C code. You
probably can't go further, however, at least not in C, since that would
require a C comment inside a C comment.
@PP
It's possible to get quite long Lout insertions, with a bit of
care. For example, here's how to get a filled paragraph of text
into a computer program:
@ID @OneRow @Code @Verbatim {
@Eiffel {
--@@ID ragged @Break {
--@This program is free software; you can redistribute
--@it and"/"or modify it under the terms of the
--@@B { GNU General Public License } as published by
--@the Free Software Foundation; either Version 2, or
--@(at your option) any later version.
--@}
launch(x: APPLICATION) is
-- launch the application
deferred
}
}
produces
@ID @OneRow @Eiffel {
--@@ID ragged @Break {
--@This program is free software; you can redistribute
--@it and"/"or modify it under the terms of the
--@@B { GNU General Public License } as published by
--@the Free Software Foundation; either Version 2, or
--@(at your option) any later version.
--@}
launch(x: APPLICATION) is
-- launch the application
deferred
}
This example relies on the fact that @Code prg2lout passes
escape comments like these through to Lout absolutely
untouched. Notice the use of both a display symbol ({@Code "@ID"})
and a change to the break style ({@Code "ragged @Break"}). If
the change of break style had been omitted, the break
style of the surrounding program, {@Code "lines @Break"},
would have been applied to the displayed paragraph. The
display symbol is needed because without it the paragraph
would be an integral part of the surrounding program (which
is actually considered by Lout to be one paragraph), making
the @Code "ragged @Break" ineffective since you can't change
the paragraph style in the middle of a paragraph.
@PP
Clearly, use of such escape comments in conjunction with line
numbers is going to be problematic. No promise is made
that the result of doing that will make sense.
@End @Section
|
