Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | For the requirements matrix, scan evidence marks in the original source code, not in the amalgamation. Updates to SQL comment documentation. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
dca51f132e086488cad17283edec4ff7 |
| User & Date: | drh 2009-12-14 17:41:11 |
Context
|
2009-12-14
| ||
| 23:00 | Identify requirements in the autoinc.html and datatype3.html documents. Make corrections in datatype3.html for accuracy and for clearer presentation. check-in: e18ce3ebd0 user: drh tags: trunk | |
| 17:41 | For the requirements matrix, scan evidence marks in the original source code, not in the amalgamation. Updates to SQL comment documentation. check-in: dca51f132e user: drh tags: trunk | |
|
2009-12-13
| ||
| 23:03 | Additional cleanup in the SQL language documentation. check-in: d508b9e21c user: drh tags: trunk | |
Changes
Changes to main.mk.
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
..
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
# scan_test_cases.tcl for additional information. # # The output file evidence.txt is used by requirements coverage analysis. # SCANNER = $(DOC)/scan_test_cases.tcl evidence: tclsh ./tclsh $(SCANNER) -reset src $(TCLSQLITE3C) ./tclsh $(SCANNER) tcl $(SRC)/test/*.test if test '' != '$(TH3)'; then \ ./tclsh $(SCANNER) th3 $(TH3)/mkth3.tcl; \ ./tclsh $(SCANNER) th3/req1 $(TH3)/req1/*.test; \ ./tclsh $(SCANNER) th3/cov1 $(TH3)/cov1/*.test; \ fi ................................................................................ # Copy and HTMLize evidence files # FMT = $(DOC)/format_evidence.tcl format_evidence: tclsh mkdir -p doc/matrix/ev rm -f doc/matrix/ev/* ./tclsh $(FMT) src doc/matrix $(TCLSQLITE3C) ./tclsh $(FMT) tcl doc/matrix $(SRC)/test/*.test private_evidence: format_evidence ./tclsh $(FMT) th3 doc/matrix $(TH3)/mkth3.tcl ./tclsh $(FMT) th3/req1 doc/matrix $(TH3)/req1/*.test ./tclsh $(FMT) th3/cov1 doc/matrix $(TH3)/cov1/*.test |
|
>
>
|
>
>
|
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
..
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
# scan_test_cases.tcl for additional information. # # The output file evidence.txt is used by requirements coverage analysis. # SCANNER = $(DOC)/scan_test_cases.tcl evidence: tclsh ./tclsh $(SCANNER) -reset src $(SRC)/src/*.[chy] ./tclsh $(SCANNER) src $(SRC)/ext/fts3/*.[ch] ./tclsh $(SCANNER) src $(SRC)/ext/rtree/*.[ch] ./tclsh $(SCANNER) tcl $(SRC)/test/*.test if test '' != '$(TH3)'; then \ ./tclsh $(SCANNER) th3 $(TH3)/mkth3.tcl; \ ./tclsh $(SCANNER) th3/req1 $(TH3)/req1/*.test; \ ./tclsh $(SCANNER) th3/cov1 $(TH3)/cov1/*.test; \ fi ................................................................................ # Copy and HTMLize evidence files # FMT = $(DOC)/format_evidence.tcl format_evidence: tclsh mkdir -p doc/matrix/ev rm -f doc/matrix/ev/* ./tclsh $(FMT) src doc/matrix $(SRC)/src/*.[chy] ./tclsh $(FMT) src doc/matrix $(SRC)/ext/fts3/*.[ch] ./tclsh $(FMT) src doc/matrix $(SRC)/ext/rtree/*.[ch] ./tclsh $(FMT) tcl doc/matrix $(SRC)/test/*.test private_evidence: format_evidence ./tclsh $(FMT) th3 doc/matrix $(TH3)/mkth3.tcl ./tclsh $(FMT) th3/req1 doc/matrix $(TH3)/req1/*.test ./tclsh $(FMT) th3/cov1 doc/matrix $(TH3)/cov1/*.test |
Changes to pages/lang.in.
526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 |
<tcl>
###############################################################################
Section comment comment {comment *comments}
BubbleDiagram comment-syntax
</tcl>
<p>Comments are not SQL commands, but can occur within the text of
SQL queries passed to [sqlite3_prepare_v2()] and related interfaces..
^Comments are treated as whitespace by the parser.
^Comments can begin anywhere whitespace
can be found, including inside expressions that span multiple lines.
</p>
<p>^SQL comments begin with two consecutive "-" characters (ASCII 0x2d)
and extend up to and including the next newline character (ASCII 0x0a)
or until the end of input, whichever comes first.</p>
<p>^C comments can span any number of lines. C-style comments begin
with "/*" and extend up to and including the next "*/" character pair
or until the end of input, whichever comes first. ^C-style comments
can span multiple lines. </p>
<p>^Comments can appear anywhere whitespace can occur,
including inside expressions and in the middle of other SQL statements.
^Comments do not nest.
|
| | | |
526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 |
<tcl>
###############################################################################
Section comment comment {comment *comments}
BubbleDiagram comment-syntax
</tcl>
<p>^Comments are not SQL commands, but can occur within the text of
SQL queries passed to [sqlite3_prepare_v2()] and related interfaces.
^Comments are treated as whitespace by the parser.
^Comments can begin anywhere whitespace
can be found, including inside expressions that span multiple lines.
</p>
<p>^SQL comments begin with two consecutive "-" characters (ASCII 0x2d)
and extend up to and including the next newline character (ASCII 0x0a)
or until the end of input, whichever comes first.</p>
<p>^C-style comments begin
with "/*" and extend up to and including the next "*/" character pair
or until the end of input, whichever comes first. ^C-style comments
can span multiple lines. </p>
<p>^Comments can appear anywhere whitespace can occur,
including inside expressions and in the middle of other SQL statements.
^Comments do not nest.
|