diff options
author | Jesse Vincent <jesse@bestpractical.com> | 2010-04-13 16:47:49 -0400 |
---|---|---|
committer | Jesse Vincent <jesse@bestpractical.com> | 2010-04-13 16:47:49 -0400 |
commit | 1f317c954d04a08fbd69324135531f89b95bd969 (patch) | |
tree | b7339d94061fd8360b25232d5b2da3705b45ca7c | |
parent | 6b5ec6e4fa6ef6732ba89d1614d3c98944138a22 (diff) | |
download | perl-1f317c954d04a08fbd69324135531f89b95bd969.tar.gz |
Revert "Revert "* Fixed typo in toke.c docs, identified by Zefram""
This reverts commit 06164d6c3ad67ed7ba18030ae378f46f482a29af.
-rw-r--r-- | toke.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -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. |