summaryrefslogtreecommitdiff
path: root/pod
Commit message (Collapse)AuthorAgeFilesLines
* Regenerate from meta after backporting crosscompile changesH.Merijn Brand2014-01-221-0/+1
| | | | | I am sure there are items that could have been processed even cleaner, but with the current state, the content is functional equal.
* perldelta for c91312d5e, none needed for e214621beTony Cook2014-01-221-1/+4
|
* assume "all" in "use warnings 'FATAL';" and relatedHauke D2014-01-221-0/+13
| | | | | | | | | | | | | Until now, the behavior of the statements use warnings "FATAL"; use warnings "NONFATAL"; no warnings "FATAL"; was unspecified and inconsistent. This change causes them to be handled with an implied "all" at the end of the import list. Tony Cook: fix AUTHORS formatting
* add a missing word in perllexwarnHauke D2014-01-221-1/+1
|
* document $^P's 0x800 and 0x1000Ricardo Signes2014-01-201-0/+8
| | | | these were introduced in c30d8139e
* create new perldelta for 5.19.9Ricardo Signes2014-01-204-266/+170
|
* perldelta: add the 5.19.8 acknowledgementsv5.19.8Ricardo Signes2014-01-201-3/+26
|
* perlhist: note that 5.19.8 should be released todayRicardo Signes2014-01-201-0/+1
|
* pod/perllexwarn.pod: clarify note about the "deprecated" categoryÆvar Arnfjörð Bjarmason2014-01-191-1/+1
| | | | | | | | | | Saying that something used to behave a certain way "In Perl 5.6.1" can be understood as it changing in 5.6.2, but in fact this change to the "deprecated" category in perl-5.6.0-8156-g12bcd1a was never released in any 5.6.* release, it was first released in 5.8.0. So note that explicitly instead, it's less ambiguous to just say "Before Perl 5.8.0".
* perldelta: update module changesRicardo Signes2014-01-191-7/+107
| | | | | used Porting/corelist-perldelta.pl! thanks Abir Viqar and Steve Hay!
* perldelta: prune unused sections and markersRicardo Signes2014-01-191-202/+0
|
* perldelta for 1850f57fRicardo Signes2014-01-191-1/+2
|
* perldelta for addition of IO-Socket-IPRicardo Signes2014-01-191-1/+1
|
* fix broken perl5197deltaRicardo Signes2014-01-191-1/+414
|
* perldelta for bfa371b621Father Chrysostomos2014-01-181-0/+5
|
* perldelta for f60e676307Father Chrysostomos2014-01-181-0/+9
|
* perldelta typoFather Chrysostomos2014-01-181-1/+1
|
* perldiag: Rewrap autoderef entriesFather Chrysostomos2014-01-181-21/+24
| | | | for better splain output
* perldelta for 88c342510b9Father Chrysostomos2014-01-181-0/+6
|
* perldelta for 6567ce2473Father Chrysostomos2014-01-181-0/+7
|
* Mention perlbug -p in perlhack.Craig A. Berry2014-01-171-11/+9
| | | | | Using git's --attach with perlbug -f actually mangled the patches, making them harder to apply, but now we have a better way to do it.
* perldelta for perlbug changes.Craig A. Berry2014-01-171-2/+7
|
* perldelta for 901ee108feFather Chrysostomos2014-01-171-0/+5
|
* perldelta for ceaf124e0Father Chrysostomos2014-01-171-1/+3
|
* perldiag for new mprotect warningsFather Chrysostomos2014-01-161-2/+17
|
* COW documentationFather Chrysostomos2014-01-161-0/+48
| | | | | plus read-only documentation, since hysterically the two are intertwined.
* describe the level of FreeMINT supportTony Cook2014-01-161-0/+8
|
* perldelta for 6a601575dcTony Cook2014-01-161-0/+7
|
* perldelta for e122534c08Tony Cook2014-01-151-2/+6
|
* perldelta for 24fc4d43fdTony Cook2014-01-151-0/+3
|
* perldelta for experimental::autoderefRicardo Signes2014-01-141-1/+18
|
* rename aggref warnings to autoderefRicardo Signes2014-01-142-17/+17
|
* Make key/push $scalar experimentalFather Chrysostomos2014-01-142-2/+68
| | | | | We need a better name for the experimental category, but I have not thought of one, even after sleeping on it.
* perldelta for 466947750 and cf74bc378c0Tony Cook2014-01-141-0/+7
|
* perldelta for -DsysrootBrian Fraser2014-01-141-0/+10
|
* perldelta for c3970b8037Tony Cook2014-01-131-0/+6
|
* perldiag: Rewrap an entry for better splain outputFather Chrysostomos2014-01-101-5/+5
|
* perldiag: Use (F) consistentlyFather Chrysostomos2014-01-101-5/+4
| | | | | and explain in the prose when there is an error. One entry already explained this.
* Correct capitalization of Devel::ptkdb in perldebugBrian Gottreu2014-01-111-2/+2
|
* perlfunc: 'if' is in perlsyn, not perlopKarl Williamson2014-01-091-2/+2
| | | | Thanks to Hauke D for pointing this out.
* pod/perlrecharclass: Document [:blank:], [:ascii:] for C89 platformsKarl Williamson2014-01-091-2/+19
| | | | | These POSIX classes were introduced in C99, and not all C89 platforms recognize them. The behavior there was previously undocumented
* pod/perlrecharclass: NitsKarl Williamson2014-01-091-9/+11
|
* add 5.18.2 to perlhistRicardo Signes2014-01-071-0/+1
|
* Upgrade libnet from version 1.23 to 1.24Steve Hay2014-01-061-0/+6
|
* perldelta for d_libname_uniqueBrian Fraser2014-01-041-1/+6
|
* perldiag.pod: Correct some categoriesKarl Williamson2014-01-031-6/+8
| | | | | | | | | The warning categories were wrong in a few places here. diag.t had them as to ignore. By correcting them in the pod, they can be removed from the ignore list. This commit additionally adds text for a few messages that can be either fatal or just warnings.
* Upgrade Encode from version 2.56 to 2.57Steve Hay2014-01-031-1/+4
|
* perldiag: Rewrap an entry slightlyFather Chrysostomos2014-01-021-3/+3
| | | | for better splain output
* Change some warnings in utf8n_to_uvchr()Karl Williamson2014-01-011-3/+17
| | | | | | | | | | | | | | | | This bottom level function decodes the first character of a UTF-8 string into a code point. It is discouraged from using it directly. This commit cleans up some of the warnings it can raise. Now, tests for malformations are done before any tests for other potential issues. One of those issues involves code points so large that they have never appeared in any official standard (the current standard has scaled back the highest acceptable code point from earlier versions). It is possible (though not done in CPAN) to warn and/or forbid these code points, while accepting smaller code points that are still above the legal Unicode maximum. The warning message for this now includes the code point if representable on the machine. Previously it always displayed raw bytes, which is what it still does for non-representable code points.
* utf8.c: Fix warning category and subcategory conflictsKarl Williamson2014-01-011-1/+1
| | | | | | | | | | | | | | | | The warnings categories non_unicode, nonchar, and surrogate are all subcategories of 'utf8'. One should never call a packWARN() with both a category and a subcategory of it, as it will mean that one can't completely make the subcategory independent. For example, use warnings 'utf8'; no warnings 'surrogate'; surrogate warnings will be output if they are tested with a ckWARN2(WARN_UTF8, WARN_SURROGATE); utf8.c was guilty of this.
View Lorry Controller Status