diff options
author | Andreas Rumpf <rumpf_a@web.de> | 2018-04-02 17:01:40 +0200 |
---|---|---|
committer | Andreas Rumpf <rumpf_a@web.de> | 2018-04-02 17:01:40 +0200 |
commit | b25044286b1929a2939a7e57991afab96b1f2ffe (patch) | |
tree | f46862789b214eb9d9450f1a89ac0971ab517461 /lib/system/sysstr.nim | |
parent | cc6fe6e5786f53f15c434dc10912418a470bb64a (diff) | |
download | Nim-b25044286b1929a2939a7e57991afab96b1f2ffe.tar.gz |
sysstr.nim: fix minor typos
Diffstat (limited to 'lib/system/sysstr.nim')
-rw-r--r-- | lib/system/sysstr.nim | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/system/sysstr.nim b/lib/system/sysstr.nim index 5bf90c895..ea0273340 100644 --- a/lib/system/sysstr.nim +++ b/lib/system/sysstr.nim @@ -293,7 +293,7 @@ proc setLengthSeq(seq: PGenericSeq, elemSize, newLen: int): PGenericSeq {. # XXX: zeroing out the memory can still result in crashes if a wiped-out # cell is aliased by another pointer (ie proc parameter or a let variable). - # This is a tought problem, because even if we don't zeroMem here, in the + # This is a tough problem, because even if we don't zeroMem here, in the # presence of user defined destructors, the user will expect the cell to be # "destroyed" thus creating the same problem. We can destoy the cell in the # finalizer of the sequence, but this makes destruction non-deterministic. @@ -420,7 +420,7 @@ proc nimParseBiggestFloat(s: string, number: var BiggestFloat, return 0 if s[i] in {'0'..'9'}: - first_digit = (s[i].ord - '0'.ord) + first_digit = (s[i].ord - '0'.ord) # Integer part? while s[i] in {'0'..'9'}: inc(kdigits) |