| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
After much alternation, altercation and alteration, __SUB__ is
finally here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is no reason why constant redefinition warnings should be
default warnings for sub foo(){1}, but not for newCONSTSUB (which
calls newXS, which triggers the warning).
To make this work properly, I also had to import sv.c’s ‘are these
const subs from the same SV originally?’ logic. Constants created
with XS can have NULL for the SV (they return an empty list or
&PL_sv_undef), which means sv.c’s logic will stop *this=\&that from
warning if both this and that are such XS-created constants.
newCONSTSUB needed to be consistent with that. It required tweaking a
test I added a few commits ago, which arguably shouldn’t have warned
the way it was written.
As of this commit (and before it, too, come to think of it),
newXS_len_flags’s calling convention is quite awful and would need to
be throughly re-thunk before being made into an API, or probably sim-
ply never made into an API.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
newCONSTSUB uses the compile-time warning hints, instead of the run-
time hints. This means that
use warnings;
BEGIN {
no warnings;
some_XS_function_that_calls_new_CONSTSUB();
}
may trigger a redefinition warning, whereas it should be analogous to
use warnings;
BEGIN {
no warnings;
*foo = \&bar;
}
which does not warn.
newCONSTSUB localises PL_curcop and sets it to &PL_compiling. When it
does that, it needs to copy the hints over.
Running tests inside eval is not reliable without a test count, so I
added one.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Due to the '.' in 'test.lib's name, t/filenames.t fails (because '.' is the path
separator on VMS). To fix this, I create and delete the directory and its
contents during each test that needs to access the directory. Said tests will be
skipped if the directory cannot be created (e.g., on VMS).
|
| | |
|
| |
| |
| |
| | |
This fixes the podcheck error complaining about their filenames
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
$cwd already includes $volume
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
I added a whole bunch of "File::Spec"s and "File::Spec::Unix"s and I
updated the test cases and test harness to be platform independent.
I also updated some documentation in Pod::Html and removed some unneeded code.
|
| |
| |
| |
| | |
Take into account Windows paths in Podroot and Podpath
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Correct the lack of possible offset when removing Podroot from each
Podpath to account for a trailing slash in Podroot.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
It converts more and correctly converts anchored =head directives and
index elements
|
| |
| |
| |
| |
| | |
The bug prevented '<body id="_podtop_">' from appearing when
--backlink was enabled
|
| |
| |
| |
| |
| | |
Note that it uses <b> instead of <strong>, <i> instead of <em>,
and converts E<> formatting codes before they are written to .html
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The script does basic conversion of old Pod::HTMl test cases to new
Pod::Html test cases.
|
| |
| |
| |
| |
| |
| |
| | |
The bug inhibited finding replacement paths for POD documents not found
in %Pages.
Update the accompanying warning message, too.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The bug stopped POD files from being crossreferenced if they were more
than one directory below $Podpath
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
I remove $Podroot in the ::Search callback for correct crossreferencing.
I update @Podpath mapping to use File::Spec instead of normal string concat
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Libpods was used to implicitly convert C<> text to links given
that the C<>text was also the text of an =item directive in any
particular perldoc.
I do not plan on reimplementing this feature, or any implicit
linkification for that matter.
|
| | |
|