diff options
author | Jesse Vincent <jesse@bestpractical.com> | 2010-04-12 08:43:28 -0400 |
---|---|---|
committer | Jesse Vincent <jesse@bestpractical.com> | 2010-04-12 08:43:28 -0400 |
commit | 06164d6c3ad67ed7ba18030ae378f46f482a29af (patch) | |
tree | 9a72196d8746cbbc5c67c24d2689ba03e29f83b6 /toke.c | |
parent | 675ac12c19e6fe00eff6e604a7d637bf621997ef (diff) | |
download | perl-06164d6c3ad67ed7ba18030ae378f46f482a29af.tar.gz |
Revert "* Fixed typo in toke.c docs, identified by Zefram"
The commit was good, but we're in freeze for 5.12.0. I'd be happy to
see this hit blead again after 5.12.0 is tagged.
This reverts commit 675ac12c19e6fe00eff6e604a7d637bf621997ef.
Diffstat (limited to 'toke.c')
-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 for +and the lexing code has kept multiple lines of text in the buffer fof 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. |