ExternalVendorCode/conserver
1
0
Fork 0
mirror of https://github.com/bstansell/conserver.git synced 2025-03-24 21:05:19 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

improve description of the #include statement

Browse Source 
The #include statement must be preceded by a blank line!
This commit is contained in:
Greg A. Woods 2021-03-21 15:57:08 -07:00
parent 5cd5df957c
commit 24288a1221
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
conserver.cf/conserver.cf.man.in
View File

@ -62,6 +62,7 @@ console simple {
.PP
The parser has six characters that it considers special.
These are: ``{'', ``}'', ``;'', ``#'', ``\e'', and ``"''.
.\" "
The first three (hereby called tokens) define the format of the
configuration blocks and are used as word
separators, the next is the comment character, and the last two are
@ -96,6 +97,7 @@ If a character is prefixed by a backslash, the next character is a
literal (so ``\e\e'' produces a ``\e'', ``\e"'' produces ``"'', ``\e{''
produces a ``{'', etc.).
For double-quoted strings, all characters are literal except for ``\e"'',
.\" "
which embeds a double-quote.
.PP
Adding a variety of quotes to our example without changing the meaning
@ -107,9 +109,12 @@ of things, we have:
.fi
.ft
.PP
There is one special line the parser recognizes: a ``#include'' statement.
There is one special line the parser recognizes: a ``#include''
statement, but only if it is preceded by a blank line.
It is of the form:
.IP
# a normal comment line followed by a blank line
.IP
.B #include
.I filename
.PP