| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
fields are correct
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
like "2 months" between two dev releases
There were a couple bugs ...
First, we should just use the date of the two commits we're looking at rather
than looking at all the commits in between and picking the earliest one. This
can find _much_ earlier things that weren't merged until much later, which
really throws the numbers off.
Second, when calculating the number of weeks and months, we shouldn't use
POSIX::ceil(), that rounds up 4.01 weeks to 5. Instead, I wrote a simple
rounding function that does standard rounding.
|
|
|
|
|
| |
The utilities from utils.lst end with a .com extension, and the
pseudo-shebang line looks quite different.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
When seeing whether the cop hint hash contains the given feature,
Perl_feature_is_enabled only needs to see whether the hint hash ele-
ment exists. It doesn’t need to turn it into a scalar.
|
|
|
|
|
|
|
|
| |
The package name should not be omitted when the name begins with punc-
tuation unless the variable is in the main package.
"]"->[0] is force into the main package.
"a::]"->[0] is not.
|
|
|
|
|
|
| |
This commit finishes the work done by b89b7257 and be6cf5cf0a by mak-
ing "string"->[...] and "string"->{...} in general deparse correctly
when "string" is not a valid identifier.
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
Changes for 0.30 Wed Dec 21 23:30:39 GMT 2011
=====================================================
* Resolve PAUSE indexer problems
Changes for 0.28 Wed Dec 21 22:26:05 GMT 2011
=====================================================
* Apply Debian patches [rt.cpan.org #73400]
|
|
|
|
|
|
|
|
|
|
|
| |
In Porting/Maintainers.pl CUSTOMIZED is a list of files that have been
customized within the Perl core. These tests make SHA digests of the
customized files and do a comparison previously stored digests to
ensure that customization is not lost when updating from upstream.
Update MANIFEST with the customized files
Add --regen ability to porting/customized.t and some documentation
|
|
|
|
|
|
|
|
|
| |
Commit 31940c077ae95db7 added some git log output. To avoid the need to
re-indent it, it was "commented out" using Pod. However, the Pod used was
buggy. It used a =for, when it should have used a =begin/=end pair.
Without this, Pod renderers display the "comment" as if it is part of the
documentation, which isn't desired.
|
|
|
|
|
|
|
|
|
|
| |
Right now, without this, it's possible to pass the all the regression tests
even if one has introduced syntax errors into scripts such as installperl
or installman. No tests fail, so it's fair game to push the commit.
Obviously this breaks installing perl, but we won't spot this.
Whilst we can't easily test that the various scripts *work*, we can at least
check that we've not made any trivial screw ups.
|
|
|
|
|
|
|
|
| |
This way ./perl -Ilib -c Porting/corelist-perldelta.pl can be used to syntax
check it.
corelist-perldelta.pl was not importing symbols from Algorithm::Diff, so
there are no changes in runtime behaviour.
|
|
|
|
|
|
|
| |
This way ./perl -Ilib -c Porting/cherrymaint can be used to syntax check it.
cherrymaint was not importing symbols from LWP::UserAgent, so there are no
changes in runtime behaviour.
|
|
|
|
|
|
|
|
|
| |
This way ./perl -Ilib -c Porting/checkURL.pl can be used to syntax check it.
Only File::Slurp and URI::Find::Simple were actually relying on C<use> to
import subroutines - replace the two uses with fully qualified names.
All other packages are needed for object constructors, not imports, so there
is no change in loading them with C<require>.
|
|
|
|
|
|
|
|
|
| |
[DELTA]
Changes for 0.9115 Tue Dec 20 21:10:24 2011
================================================
* Added new config option 'allow_unknown_prereqs'
to resolve issues with 0.9114 release
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Entries from a tied %^H were not being copied to inner compile-time
scopes, resulting in %^H appearing empty in BEGIN blocks, even
though the underlying he chain *was* being propagated properly (so
(caller)[10] at run time still worked.
I was surprised that, in writing tests for this, I produced another
crash. I thought I had fixed them with 95cf23680 and 7ef9d42ce. It
turns out that pp_helem doesn’t support hashes with null values.
(That’s a separate bug that needs fixing, since the XS API allows for
them.) For now, cloning the hh properly stops pp_helem from getting a
null value.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
"foo"->[0] and $foo[0] compile down to the same thing. B::Deparse was
assuming that an rv2gv with a gv kid would have to be $foo[0] syntax,
so it didn’t take things like '!@T#$'->[0] into account.
This commit only fixes aelemfast. It is related to b89b7257.
|
| |
|
| |
|
|
|
|
|
| |
Also mention that the site is in github and the release manager can do the
edit him or herself if they want to.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- Include the original RMG in the generated document
- Generate pod or HTML - no need for Markdent
|
| |
|
|
|
|
| |
Pod::Tidy 0.10 added this. It's cleaner than setting $Text::Wrap::columns.
|
| |
|
|
|
|
|
|
|
|
| |
The code to recursively scan a directory with File::File::find() is now only
used by one caller of podset(), so move it to the call point, reducing the
amount of conditional code within podset(). The first argument to podset()
is now always a reference to a hash of "work to be done". Add an optional
fourth argument to give the directory name for diagnostics.
|
|
|
|
|
| |
The previous instructions were unaware that most of what they describe is
already automated.
|
|\ |
|
| |
| |
| |
| | |
Now it returns just the pod's name, its filename, and the flags (if any).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The description is only used to generate MANIFEST entries now from 'readmes'
and 'pods'. now that perl.pod is the master and is no longer generated from
pod.lst
The leafname/podname distinction is only used by is_duplicate_pod(), so can
be replaced by simple flag, 'dual'.
Replace the now-unused entries with undef to preserve the indices.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Nothing uses the entries in the 'master' array for the for the elements
flagged as 'aux', so don't generate them. Only buildtoc uses the the 'aux'
hash, and only the keys in sorted order, so replace the hash with a sorted
array.
All entries in the 'master' array are now defined, and references to 5
element arrays, so remove code that checks for this. Likewise, as the 'aux'
flag is no longer used, remove code related to it.
When generating the entries for README files in %our_pods in the consistency
checking code in get_pod_metadata, $_->[4] and $_->[1] will always be equal,
as no READMEs are copied from dual life modules. So use $_->[1] instead, as
this permits a future simplification.
|
|/
|
|
|
|
|
|
| |
perl.pod already contained virtually all the information in pod.lst. Add
the remainder as =begin and =for Pod blocks.
As perl.pod no longer needs to be regenerated, remove the redundant code from
Porting/pod_rules.pl. Update (nearly) all references to pod.lst.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test that was added in 95cf23680e tickled another bug in the same
code in Perl_hv_copy_hints_hv than the one it fixed, but not on the
committer’s machine.
Not only can a HE from a tied hash have a null entry, but it can also
have an SV for its key. Treating it as a hek and trying to read flags
from it may result in other code being told to free something it
shouldn’t because the SV, when looked at as a hek, appeared to have
the HVhek_FREEKEY flag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
‘open bareword’ compiles down to
open
`--+--pushmark
`--gv
whereas ‘open "string"’ compiles down to
open
`--+--pushmark
`--rv2gv
`----gv
the same as ‘open *glob’.
B::Deparse was deparsing the child of the rv2gv, in order to deparse
things like open(my $fh...) as they were entered, instead of
open(*my $fh), which wouldn’t work. gvops were being deparsed as
the name. But this meant that ‘open "open"’ would be deparsed as
‘open open’, which does something different, ‘open’ being a keyword.
It also did that with ‘open '%^$^$%'’, which would deparse without the
quotation marks.
This commit changes the deparsing of filehandle-op -> rv2gv -> gv,
by keeping the explicit * present if the name of the gv is a valid
identifier (so open("foo") and open(*foo), which compile identi-
cally, both come out as open(*foo)), or by using quotation marks if
it is not.
|
| |
|
| |
|