Fossil

Check-in [e3066edea3]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Typo fix in previous
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: e3066edea3d0cef2cff8baaddf2cb7008c3367e27cab209dddec4db99eb692fc
User & Date: wyoung 2021-08-02 10:09:32.136
Context
2021-08-05
11:55
Resolved invalid memory write in --args FILE handling when FILE contains embedded NULs, as reported in [forum:/forumpost/7b34eecc1b8cf5d2|forum post 7b34eecc1b8cf5d2]. Cause: mismatch between --args expansion's own line counting vs blob_line() counting. All bytes after the first embedded NUL are now effectively ignored. ... (check-in: e120c2a9a7 user: stephan tags: trunk)
2021-08-02
10:09
Typo fix in previous ... (check-in: e3066edea3 user: wyoung tags: trunk)
08:49
Clarified the double-quoting and {} quoting rules for TH1 in the docs. ... (check-in: a1e415291c user: wyoung tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/th1.md.
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
name and subsequent tokens are the arguments.  In this sense, TH1 syntax
is similar to the familiar command-line shell syntax.

A token is any sequence of characters other than whitespace and semicolons.
Text inside double-quotes is a single token even if it includes
whitespace and semicolons. Text within {...} pairs is also a
single token, which is useful because curly braces are easier to “pair”
and nest properly than doubloe-quotes.

The nested {...} form of tokens is important because it allows TH1 commands
to have an appearance similar to C/C++.  It is important to remember, though,
that a TH1 script is really just a list of text commands, not a context-free
language with a grammar like C/C++.  This can be confusing to long-time
C/C++ programmers because TH1 does look a lot like C/C++, but the semantics
of TH1 are closer to FORTH or Lisp than they are to C.







|







41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
name and subsequent tokens are the arguments.  In this sense, TH1 syntax
is similar to the familiar command-line shell syntax.

A token is any sequence of characters other than whitespace and semicolons.
Text inside double-quotes is a single token even if it includes
whitespace and semicolons. Text within {...} pairs is also a
single token, which is useful because curly braces are easier to “pair”
and nest properly than double-quotes.

The nested {...} form of tokens is important because it allows TH1 commands
to have an appearance similar to C/C++.  It is important to remember, though,
that a TH1 script is really just a list of text commands, not a context-free
language with a grammar like C/C++.  This can be confusing to long-time
C/C++ programmers because TH1 does look a lot like C/C++, but the semantics
of TH1 are closer to FORTH or Lisp than they are to C.