aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorD. Bohdan <dbohdan@dbohdan.com>2020-09-08 08:52:14 +0000
committerSteve Bennett <steveb@workware.net.au>2020-09-23 10:37:52 +1000
commit0a6e801f1425225ba4b52fe91d5b75afda998a1a (patch)
tree2f89d778e598c0b8398692bccdcbc08d9341517c
parentc95e5271b69c3f04d105607d1033733d5a3ac734 (diff)
downloadjimtcl-0a6e801f1425225ba4b52fe91d5b75afda998a1a.zip
jimtcl-0a6e801f1425225ba4b52fe91d5b75afda998a1a.tar.gz
jimtcl-0a6e801f1425225ba4b52fe91d5b75afda998a1a.tar.bz2
docs: reword paragraph on integer prefixes
Thanks to @gromgit on GitHub for suggesting this phrasing.
-rw-r--r--jim_tcl.txt9
1 files changed, 4 insertions, 5 deletions
diff --git a/jim_tcl.txt b/jim_tcl.txt
index 3b0a54e..21aa066 100644
--- a/jim_tcl.txt
+++ b/jim_tcl.txt
@@ -719,11 +719,10 @@ White space may be used between the operands and operators and
parentheses; it is ignored by the expression processor.
Where possible, operands are interpreted as integer values.
-Integer values may be specified in decimal (the default case that can
-be make explicit by prepending '0d' to the operand) or in binary, octal
-or hexadecimal (if the first two characters of the operand are '0b',
-'0o' or '0x' respectively). Note that Jim Tcl does *not* treat numbers
-with leading zeros as octal.
+Integer values are interpreted as decimal, binary, octal or
+hexadecimal if prepended with '0d', '0b', '0o' or '0x'
+respectively. Otherwise they are interpreted as decimal by default.
+(Jim Tcl does not interpret numbers with leading zeros as octal.)
If an operand does not have one of the integer formats given
above, then it is treated as a floating-point number if that is