summaryrefslogtreecommitdiff
path: root/toke.c
diff options
context:
space:
mode:
authorbrian d foy <bdfoy@cpan.org>2010-04-11 14:15:27 +0200
committerbrian d foy <bdfoy@cpan.org>2010-04-11 14:15:27 +0200
commit675ac12c19e6fe00eff6e604a7d637bf621997ef (patch)
tree39f7945b216b3b9b9b5483ba46ccdd7c09a0e211 /toke.c
parent431be7b35e7448c1ced59444d6bdcfa11c5f83c7 (diff)
downloadperl-675ac12c19e6fe00eff6e604a7d637bf621997ef.tar.gz
* Fixed typo in toke.c docs, identified by Zefram
Diffstat (limited to 'toke.c')
-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.