summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2010-04-13 16:47:49 -0400
committerJesse Vincent <jesse@bestpractical.com>2010-04-13 16:47:49 -0400
commit1f317c954d04a08fbd69324135531f89b95bd969 (patch)
treeb7339d94061fd8360b25232d5b2da3705b45ca7c
parent6b5ec6e4fa6ef6732ba89d1614d3c98944138a22 (diff)
downloadperl-1f317c954d04a08fbd69324135531f89b95bd969.tar.gz
Revert "Revert "* Fixed typo in toke.c docs, identified by Zefram""
This reverts commit 06164d6c3ad67ed7ba18030ae378f46f482a29af.
-rw-r--r--toke.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/toke.c b/toke.c
index a7a71a4cea..19fce677fb 100644
--- a/toke.c
+++ b/toke.c
@@ -1124,7 +1124,7 @@ it is not permitted to discard text that has yet to be lexed.
Normally it is not necessarily to do this directly, because it suffices to
use the implicit discarding behaviour of L</lex_next_chunk> and things
based on it. However, if a token stretches across multiple lines,
-and the lexing code has kept multiple lines of text in the buffer fof
+and the lexing code has kept multiple lines of text in the buffer for
that purpose, then after completion of the token it would be wise to
explicitly discard the now-unneeded earlier lines, to avoid future
multi-line tokens growing the buffer without bound.