| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
These implement uppercase-named macros.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This defines a variable if not defined, and dates from earlier logic,
and wasn't removed when that logic changed. This line hid bugs that the
next line is supposed to catch.
|
| | |
|
| | |
|
| |
|
|
| |
pp_subst has been moved out of this file and into pp_hot.c
|
| |
|
|
|
| |
Outside code should likely be using the wrapping macros TAINT_PROPER,
TAINT_ENV
|
| |
|
|
|
|
| |
Tainting is so specialized that things dealing with it are better
gathered together in one place. This commit moves the existing docs for
such API into the new section
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds section names of what section each non-adjacent function
should go into in perlapi, perlintern.
Sections are in effect until the next command changing it. As functions
are added/removed from this file, they may inadvertently get placed in
the wrong api section by virtue of inheriting the previous section name.
Guard against that by specifying the proper section the pod for each
function that is not in the same pod /* comment */ as another function.
This change fixed a bug where one function was shown in the wrong
section in perlapi.
|
| | |
|
| |
|
|
|
|
|
| |
the F<> marker shouldn't need to be told whether or not to use "" to
demarcate its argument. It should know what to do.
Also fix some overlong verbatim lines
|
| | |
|
| | |
|
| |
|
|
| |
This makes it clearer
|
| |
|
|
|
|
| |
When rebasing, you can get conflicts. The simplest solution for a
generated file is to regenerate it. But prior to this commit, all such
lines would have to be manually removed.
|
| |
|
|
|
| |
This converts this file to follow the paradigm everywhere else, to chdir
to 't' only if 't' is a directory
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this commit, specifying --show-all caused a fire hose of messages
to appear from pods that have many known problems, and whose output is
completely suppressed normally. An example is perlepigraphs, where many
lines are verbatim quotes from literature, and hence exceed our length
limit, but we aren't going to change wrap them (some of them are
poetry), so the output from that file of that type of problem is just
completely suppressed.
This commit keeps such output suppressed while showing all other issues.
You can still get the suppressed output unsuppressed by explicitly
specifying the file on the command line.
|
| | |
|
| | |
|
| |
|
|
|
| |
This changes the indent to the minimum necessary to trigger pod verbatim
line handling. Doing so stops the wrapping in this file.
|
| | |
|
| |
|
|
| |
Fix how links are displayed, add some links
|
| | |
|
| |
|
|
| |
Use a real word instead of slang.
|
| | |
|
| |
|
|
|
| |
This makes it slightly easier for readers to understand, and a lot
easier for podcheck.t to understand
|
| | |
|
| |
|
|
|
| |
metaconfig units and plain text files aren't pod. And lines
like Perl/perl.git aren't going to be file names.
|
| |
|
|
|
| |
This does some white space changes for readability, clarifies comments
and pod.
|
| |
|
|
|
| |
In addition to being able to call this with --add_link, you can now
specify --add-link, depending on your preference.
|
| |
|
|
|
|
|
| |
This causes the output to be flushed immediately. Without this, some
options that tried to tell you that the operation would take a while to
complete would not have that message come out until it had in fact
completed. The message should be displayed immediately.
|
| |
|
|
|
| |
This line has a syntax error in it. Fix it, and split into two lines so
doesn't wrap on output in an 80 column terminal window
|
| |
|
|
| |
These internal references are linkable
|
| |
|
|
|
|
|
|
| |
I added these to surround some C<...> that have spaces so that the
output construct is guaranteed to be on a single line. These are mostly
commands to type, and it is clearer to the reader if they kept together.
I didn't bother with things that were guaranteed to be at the beginning
of a line, as they won't wrap anyway.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
The src for this tool was a mess: it started out 20 years ago as a small
utility, then grew. Lots of badly-named global variables, no code
comments about what subs do etc. This series of commits cleans things
up, refactors, adds comments etc. In theory it makes no functional
changes, and indeed as run currently it generates exactly the same
warnings.h and lib/warning.pm files as before.
|
| | |
| |
| |
| |
| | |
Since the global variable $tree was renamed $TREE, we can now rename all
the instances of a sub parameter $tre to '$tree'.
|
| | |
| |
| |
| |
| | |
Explain this structure, which is the input used to define all the
warnings.
|
| | |
| |
| |
| |
| | |
rename my($warn, $pm) to ($warn_h, $warn_pm) to make it easier to
see that they're the filehandles for warnings.h and warnings.pm
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
valueWalk() checks for a duplicate warnings name. However,
1) This is also done in walk(), so is redundant.
2) It is broken. Originally it declared @list but checked %list;
%list is global and was renamed to %CATEGORIES to make it clear it was a
global (and thus unrelated to @list). So its probably never worked.
|
| | |
| |
| |
| |
| | |
This lexical had global scope. Instead, make it a parameter to
sub valueWalk(), since it's only used temporarily by two subs.
|
| | |
| |
| |
| | |
This doesn't seem to be used any more
|
