diff options
| author | Karl Williamson <khw@cpan.org> | 2019-05-29 16:01:34 -0600 |
|---|---|---|
| committer | Karl Williamson <khw@cpan.org> | 2019-05-30 18:13:29 -0600 |
| commit | 0a60f600e691409aab41f710bbbd8801a3162143 (patch) | |
| tree | f96b3d02392dee02bb3f9c34cfdee900c9f6bdc7 /toke.c | |
| parent | 1fcde0e9beb6235547b567747353bc1b85262783 (diff) | |
| download | perl-0a60f600e691409aab41f710bbbd8801a3162143.tar.gz | |
autodoc.pl: Add N flag
This adds a check that the macro or function name for the pod entry is a
legitimate name, as almost all are. If this had been in effect, the bug
fixed by the previous commit would not have been necessary.
But there are a very few things that are documented that aren't strict
names. This adds a flag so that autodoc can be notified to not warn on
them. This will allow Devel::PPPort to not have to special case
situations like this, which it now does.
Diffstat (limited to 'toke.c')
| -rw-r--r-- | toke.c | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -831,7 +831,7 @@ Perl_parser_free_nexttoke_ops(pTHX_ yy_parser *parser, OPSLAB *slab) /* -=for apidoc AmxU|SV *|PL_parser-E<gt>linestr +=for apidoc AmxUN|SV *|PL_parser-E<gt>linestr Buffer scalar containing the chunk currently under consideration of the text currently being lexed. This is always a plain string scalar (for @@ -858,7 +858,7 @@ lexing position is pointed to by L</PL_parser-E<gt>bufptr>. Direct use of these pointers is usually preferable to examination of the scalar through normal scalar means. -=for apidoc AmxU|char *|PL_parser-E<gt>bufend +=for apidoc AmxUN|char *|PL_parser-E<gt>bufend Direct pointer to the end of the chunk of text currently being lexed, the end of the lexer buffer. This is equal to C<SvPVX(PL_parser-E<gt>linestr) @@ -866,7 +866,7 @@ end of the lexer buffer. This is equal to C<SvPVX(PL_parser-E<gt>linestr) always located at the end of the buffer, and does not count as part of the buffer's contents. -=for apidoc AmxU|char *|PL_parser-E<gt>bufptr +=for apidoc AmxUN|char *|PL_parser-E<gt>bufptr Points to the current position of lexing inside the lexer buffer. Characters around this point may be freely examined, within @@ -884,7 +884,7 @@ Interpretation of the buffer's octets can be abstracted out by using the slightly higher-level functions L</lex_peek_unichar> and L</lex_read_unichar>. -=for apidoc AmxU|char *|PL_parser-E<gt>linestart +=for apidoc AmxUN|char *|PL_parser-E<gt>linestart Points to the start of the current line inside the lexer buffer. This is useful for indicating at which column an error occurred, and |