summaryrefslogtreecommitdiff
path: root/pod
Commit message (Collapse)AuthorAgeFilesLines
* Finalise perldeltaDominic Hargreaves2012-09-221-259/+38
| | | | Includes spelling, syntax and readability fixes
* Add 5.17.4 to perlhistFlorian Ragwitz2012-09-211-0/+1
|
* add 5.16.0 sizes and filecounts to perlhistRicardo Signes2012-09-181-26/+27
| | | | | | running and using the output of Porting/perlhist_calculate.pl has not been done regularly, presumably because I had no idea that it existed!
* add 5.14.0 sizes and filecounts to perlhistRicardo Signes2012-09-181-26/+27
| | | | | | running and using the output of Porting/perlhist_calculate.pl has not been done regularly, presumably because I had no idea that it existed!
* Update perldelta for all queued maint-5.14 changesDominic Hargreaves2012-09-071-0/+98
|
* Add 5.17.3 to perlhistSteve Hay2012-09-071-0/+1
|
* regexec.c: Fix "\x{FB01}\x{FB00}" =~ /ff/iKarl Williamson2012-08-091-0/+7
| | | | | | | | | | | Only the first character of the string was being checked when scanning for the beginning position of the pattern match. This was so wrong, it looks like it has to be a regression. I experimented a little and did not find any. I believe (but am not certain) that a multi-char fold has to be involved. The the handling of these was so broken before 5.14 that there very well may not be a regression.
* PATCH: [perl #101710] Regression with /i, latin1 chars.Karl Williamson2012-08-091-0/+8
| | | | | | The root cause of this bug is that it was assuming that a string was in utf8 when it wasn't, and so was thinking that a byte was a starter byte that wasn't, so was skipping ahead based on that starter byte.
* import perlhist data for 5.16.1Ricardo Signes2012-08-091-0/+1
|
* backport perlhist.pod from 5.17.2Tony Cook2012-07-211-2/+12
|
* Update PerlCheat to 5.14H.Merijn Brand2012-03-201-58/+60
|
* Add new 5.15.9 entries to pod/perlhist.podAbigail2012-03-201-6/+11
|
* Copy perlhist.pod from blead to maint-5.14smoke-me/maint-5.14-oldDave Rolsky2011-12-211-1/+11
|
* Create perldelta for 5.14.3Florian Ragwitz2011-09-264-102/+477
|
* Add 5.14.2 to perlhistv5.14.2Florian Ragwitz2011-09-261-0/+1
|
* Delete some empty perldelta sectionsFlorian Ragwitz2011-09-211-40/+0
|
* Fix pod syntax in perldeltaFather Chrysostomos2011-09-201-1/+1
|
* perl5123delta: should have NAME perl5123deltaKarl Williamson2011-09-191-1/+1
|
* Add 5.14.2-RC1 to perlhistFlorian Ragwitz2011-09-191-0/+1
|
* Acknowledgements in perldeltaFlorian Ragwitz2011-09-191-3/+4
|
* Panic with \b and /aaKarl Williamson2011-09-081-0/+6
| | | | | This was due to my oversight in not fixing this switch statement to accommodate /aa when it was added.
* Note that PERL_GLOBAL_STRUCT is brokenFlorian Ragwitz2011-09-081-0/+22
|
* Perldelta for the CPAN updatesFlorian Ragwitz2011-09-071-0/+14
|
* Perldelta for the CVE-2011-2939 fixFlorian Ragwitz2011-09-051-0/+11
|
* Perldelta for the PerlIO::scalar COW fixFlorian Ragwitz2011-09-051-0/+7
|
* Fix a perldelta pod nitFlorian Ragwitz2011-09-051-3/+7
|
* Perldelta for read-only glob copiesFlorian Ragwitz2011-09-051-0/+5
|
* Perldelta for deleting COWs in restricted hashesFlorian Ragwitz2011-09-051-0/+6
|
* Perldelta for the tied COW string localisation fixFlorian Ragwitz2011-09-051-0/+5
|
* move "garbage collection" glossary entry where it belongsPau Amma2011-09-051-6/+6
|
* Perldelta entry for the utf8::decode COW fixFlorian Ragwitz2011-09-051-0/+6
|
* perldelta entry for File:Glob / CVE-2011-2728 fix.Craig A. Berry2011-09-041-2/+13
|
* Perldelta for the Carp memory leak fixFlorian Ragwitz2011-08-261-0/+6
|
* perldelta for 86212507Ricardo Signes2011-08-261-0/+5
|
* Perldelta for the unpack "U*" fixFlorian Ragwitz2011-08-261-0/+6
|
* Support gcc-4.x on HP-UX PA-RISC/64H.Merijn Brand2011-08-261-1/+8
| | | | | | | | | | | | | | | | | | | Correct the socketsize. Probably due to big-endian versus little-endian, this has always worked on Intel CPUs. This is a very very old problem, and it has been the reason I never used gcc-4 on PA-RISC, because perl would not pass the test suite in 64bitall. Noticeable effects of wrong "$socksizetype" are return codes of 0 (pass) from functions like getpeername (), but invalid (or none) data in the returned structures or a return length of 0 or 256. In the latter case, the length is stored in the second part of the 64bit long and the 32bit first part is 0. This might be true on Intel-like machines too, but the tests will pass, as the significant part of the returned length is in the first 32bits and a pointer to int will still see that correct. Mind that in that case the 32bits after that might have been overridden => can of worms.
* Perldelta for the @INC filter fixesFlorian Ragwitz2011-08-261-1/+10
|
* Create a perldelta for 5.14.2Florian Ragwitz2011-08-264-229/+381
|
* A pod nitv5.14.1-RC1Jesse Vincent2011-06-091-1/+1
|
* typo fixJesse Vincent2011-06-091-1/+1
|
* more perldelta nitsJesse Vincent2011-06-091-7/+14
|
* Removing XXX sections from perldeltaJesse Vincent2011-06-091-114/+5
|
* Fix pod syntax errorsJesse Vincent2011-06-091-3/+5
|
* Documented the most recent cherrypick.Jesse Vincent2011-06-091-0/+5
|
* cherry-pick a delta entry from bleadJesse Vincent2011-06-091-0/+10
|
* snapshot perldelta workJesse Vincent2011-06-091-81/+60
|
* Add a release date for 5.14.1 to perlhist.Jesse Vincent2011-06-081-1/+3
| | | | Add a track marker for maint-5.14 to perlhist
* perldelta updateFather Chrysostomos2011-06-071-3/+75
|
* PATCH: perlop.podTom Christiansen2011-06-051-199/+282
| | | | (cherry picked from commit c543c01b43a4b95a6edf7898cea8c4662740151a)
* General perlfunc edit; document ‘default’Tom Christiansen2011-06-051-392/+499
| | | | (cherry picked from commit 8f1da26d544e0a10ac9cc91249e2e6e57e1847f6)
View Lorry Controller Status