summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Speed up csh_globFather Chrysostomos2011-10-261-21/+21
| | | | | | | | If it’s not going to be using the pattern at all (due to iteration), there is absolutely no point in parsing it. This will speed up CORE::glob and <...> as well, since they use csh_glob by default.
* Update HTTP-Tiny to CPAN version 0.015Chris 'BinGOs' Williams2011-10-264-5/+6
| | | | | | | | | | | | | | [DELTA] 0.015 2011-10-26 16:42:26 America/New_York [BUG FIXES] - Make sure PERL_UNICODE doesn't affect PUT test data [Tony Cook] [DOCUMENTATION] - Fixed typo
* bisect-runner.pl can now build all revisions on sparc64 Linux.Nicholas Clark2011-10-261-0/+79
| | | | | | | test_prep back to 5.001n, miniperl back to 5.000, for both 32 and 64 bit. This requires backporting tweaks to the Linux hints file, and patching early Configure to detect byteorder correctly as 87654321 when using linker flags to build 64 bit.
* bisect-runner.pl should patch unreliable C symbol detection code.Nicholas Clark2011-10-261-0/+60
| | | | | | Fix Configure's symbol detection to that of commit 373dfab3839ca168 if it's any intermediate version 5129fff43c4fe08c or later, as the intermediate versions don't work correctly on (at least) Sparc Linux.
* bisect-runner.pl now patches several build-busting-bugs between 5.004 & 5.005Nicholas Clark2011-10-261-0/+115
| | | | | | | This significantly reduces the number of "skip" revisions between 5.004 and 5.005, at worst speeding up bisects for problems which originate at this time, at best permitting git bisect to locate the actual commit, instead of a range of "skip"s.
* bisect-runner.pl now copes when historical MANIFEST files list directories.Nicholas Clark2011-10-261-1/+3
| | | | | | It had assumed that MANIFEST only listed files, which caused its 'force-manifest' code to choke on revisions between 27332437a2ed1941 and bf3d9ec563d25054^ inclusive, as manifest contains ext/Thread/Thread
* Update ExtUtils-MakeMaker to CPAN version 6.63_01Chris 'BinGOs' Williams2011-10-2638-148/+378
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [DELTA] 6.63_01 Sun Oct 23 16:57:24 PDT 2011 Bug Fixes * Stray $ in the PPD and meta files (for example, from the ABSTRACT) are now escaped. [rt.cpan.org 71847] Possibly incompatible changes * echo() now escapes all dollar signs by default New Features * echo() has an option to allow make variable expansion. * echo() is now passed a hash of options (old style $appending flag still works for compatibility). * quote_literal() now escapes dollar signs, but allows make variables. * quote_literal() has an option to escape make variables. * escape_dollarsigns() to escape dollar signs but allow variables * escape_all_dollarsigns() to escape all dollar signs Improvements * The PPD VERSION is now derived from the VERSION variable in the Makefile rather than hard coded. Bundled Modules * Updated CPAN::Meta to 2.112621 * Updated CPAN::Meta::YAML to 0.004 * Updated JSON::PP to 2.27200 6.62 Sun Oct 23 16:43:36 PDT 2011 No changes from 6.61_01
* Make new basic.t glob tests work on Win & VMSFather Chrysostomos2011-10-241-4/+7
| | | | | I forgot about the default PERL_EXTERNAL_GLOB setting on VMS and the special treatment of backslashes on Windows in bsd_glob.c.
* Correct comment in Glob.pmFather Chrysostomos2011-10-241-1/+1
| | | | <...> is a double-quotish construct.
* Remove part of intrpvar.h commentFather Chrysostomos2011-10-241-3/+1
| | | | This second sentence is no longer true as of 87b9e160.
* Make File::Glob::csh_glob consisent wrt '"\Father Chrysostomos2011-10-242-6/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | File::Glob::csh_glob, which is the routine implementing Perl’s own glob function, is not consistent in its treatment of quotation marks and backslashes. It differs depending on whether there are white- space characters in the pattern both preceded and followed by non- whitespace. Without whitespace, quotation marks are treated literally and back- slashes are treated as escapes that cause metacharacters to be treated literally. So <"foo*"> looks for files with literal quotation marks in their name. With whitespace, quotation marks are treated as word delimiters, so <"foo copy*"> will find file names matching /^foo copy/. Backslash escapes are pro- cessed twice, so one has to write glob '\\\** .\\\**' to find files beginning with a literal ‘*’ or ‘.*’. But simply glob '\**' to find files beginning with ‘*’. (Note that <> is a double-quotish operator, so in <> those would have to be quadruple and double back- slashes, respectively.) There are two problems with the code: 1) Text::Parsewords is only used when there is whitespace present. It should be used also for quotation marks, too, if they exist. 2) Text::Parsewords should not be removing backslash escapes. 3) Actually, there’s a third. A final escaped space should also go through Text::ParseWords, instead of being stripped. This commit fixes both things.
* In bisect-runner.pl, default to 'cc' not 'gcc'.Nicholas Clark2011-10-241-2/+2
| | | | | With this, bisect-runner.pl can build on Solaris (at least x86 Solaris) back to 5.000.
* Make <~> work again under miniperlFather Chrysostomos2011-10-242-3/+15
| | | | | | | | | | | | Commit a3342be368 localised %ENV before calling csh for glob. But that causes <~> to stop working. So this commit clears out %ENV *except* for $ENV{HOME}. It relies on the way magic works: Before localising the %ENV hash, it retrieves its $ENV{HOME} element, which is a magical scalar. It calls get-magic to store the value in the scalar itself, localises %ENV, and then calls set-magic on the element, to signal (deceitfully) that an assignment has just happened. So the cached value in the magical sca- lar is used and assigned to the env var.
* Add unit tests for Socket::{pack,unpack}_ipv6_mreqPaul \"LeoNerd\" Evans2011-10-242-0/+27
| | | | TonyC: add new ipv6_mreq.t test script to MANIFEST
* Wrap some IPv6 sockopt constants and ipv6_mreq structurePaul \"LeoNerd\" Evans2011-10-243-1/+79
|
* Add another e-mail address for Jim MeyeringFather Chrysostomos2011-10-231-0/+2
|
* don't segfault given string repeat count larger than 2^31Jim Meyering2011-10-233-6/+6
| | | | | | | | | | | E.g., this overflows INT_MAX and overruns heap memory: $ perl -le 'print "v"x(2**31+1)' [Exit 139 (SEGV)] (Perl_repeatcpy): Use the same type for "count" as our sole callers in pp.c: IV (long), not I32 (int). Otherwise, passing the wider value to a narrower "I32 count"
* ignore extra build product from ext/arybase/Tony Cook2011-10-241-0/+1
|
* fix g++ build breakage introduced in 03d9f026ae25Tony Cook2011-10-242-7/+7
| | | | C++ requires a cast to convert from void * to other types.
* perlfunc: List readpipe with qxFather Chrysostomos2011-10-231-1/+2
|
* Add Laurent Dami to AUTHORSFather Chrysostomos2011-10-231-0/+1
|
* Test dumpvar.pl with objects whose classes contain ‘=’Father Chrysostomos2011-10-231-0/+4
|
* Examining objects through the 'x' command in the perl debugger doesn'tLaurent Dami2011-10-231-2/+1
| | | | | | work if those objects are blessed into class names containing '='. This is due to incorrect parsing through 'split' in dumpvar.pl line 165.
* Synchronise Module::CoreList version in Maintainers.pl with CPANChris 'BinGOs' Williams2011-10-231-1/+1
|
* Update Unicode-Collate to CPAN version 0.81Chris 'BinGOs' Williams2011-10-2332-242/+730
| | | | | | | | | [DELTA] 0.81 Sun Oct 23 21:32:36 2011 - U::C::Locale newly supports locales: ml, mr, or, pa. - added loc_ml.t, loc_mr.t, loc_or.t, loc_pa.t in t. - updated some locales to CLDR 2.0 : mk, mt, nb, nn, ro, ru.
* bisect-runner.pl now builds test_prep on OpenBSD back to 5.002Nicholas Clark2011-10-231-0/+309
| | | | | | | | | | | | | The historical OpenBSD hints file needs tweaking for compiler and linker flags, and needs to be provided for revisions before it was added to the source tree. perl.h and pp_sys.c need patching with the current (i.e. post 1996) #ifdef forest for [gs]etpgrp() variants. perl.h needs to include <unistd.h> on OpenBSD, else POSIX.xs won't build. OpenBSD also requires all the parallel Makefile fixes, as its make builds targets in reverse lexical order, which reveals a lot of assumptions about build order. (Such as Cwd nearly always being built in time, because it sorts lexically far ahead of other XS modules dependant on it.)
* bisect-runner.pl must patch Makefile.SH to avoid parallel make problems.Nicholas Clark2011-10-231-7/+71
| | | | | | | | | | | | | | | | | Patch in all 4 "extra_dep" rules for XS modules if any are needed as it simplifies the implementation. It does no harm to have dependency rules for XS modules "from the future", as they are ignored if the module is not present. None were needed before Cwd was first converted to an XS module, so use that as the test for applicability. Remove a short-lived set of Makefile rules that attempted to run the regen scripts if needed (commits 9fec149bb652b6e9 and 5bab1179608f81d8), as they obscure whether correctly regenerated headers were checked in, and can cause spurious rebuilds or timing-related parallel make failures. Remove the code to explicitly set @INC in POSIX's Makefile.PL, as the @INC it sets will cause build failures with make_ext.pl if Cwd isn't built first, whereas the @INC set by make_ext.pl has no such issue.
* bisect-runner.pl now runs the testcase for targets config.{sh,h}Nicholas Clark2011-10-231-1/+5
| | | | | | | | | | Previously for these two targets it assumed --test-build if a --match wasn't supplied, and never ran a test case if one was supplied. Now --test-build must be specified explicitly, otherwise the test case will be run. For example, this makes it easy to bisect using a testcase which greps config.sh or config.h. (Of course, one can do roughly this with the --match option, but this will match against all generated files, which may generate false positives.)
* [perl #101486] Make PL_curstash refcountedFather Chrysostomos2011-10-228-25/+49
| | | | | | | | | | This stops PL_curstash from pointing to a freed-and-reused scalar in cases like ‘package Foo; BEGIN {*Foo:: = *Bar::}’. In such cases, another BEGIN block, or any subroutine definition, would cause a crash. Now it just happily proceeds. newATTRSUB and newXS have been modified not to call mro_method_changed_in in such cases, as it doesn’t make sense.
* Update Archive-Extract to CPAN version 0.58Chris 'BinGOs' Williams2011-10-223-13/+21
| | | | | | | | | | [DELTA] Changes for 0.58 Sat Oct 22 20:25:00 2011 ============================================ * Apply patch from Craig A. Berry [rt#71846] make _untar_bin use Unix-syntax archive names on VMS
* regexp_unicode_prop.t: Add tests.Karl Williamson2011-10-221-0/+9
| | | | | These tests make sure that a user-defined property may be included as part of another user-defined property.
* perlunicode: Fix example.Karl Williamson2011-10-221-2/+2
| | | | | | 5.14 restricted the names of user-defined property subroutines to begin with 'Is' and 'In', as has always been documented. But the example in that documentation didn't follow that restriction.
* Update perlfaq to CPAN version 5.0150036Chris 'BinGOs' Williams2011-10-2212-194/+183
| | | | | | | | | | [DELTA] 5.0150036 Sat 22 Oct 2011 16:20:34 +0100 * Website moved from faq.perl.org -> learn.perl.org (ranguard) * Delete some questions/cleanup copy (ranguard) * Make perlfaq.pod shorter/cleaner (kablamo) * Many cleanups and corrections (shlomif)
* Update HTTP-Tiny to CPAN version 0.014Chris 'BinGOs' Williams2011-10-2217-23/+582
| | | | | | | | | | | | | | | | [DELTA] 0.014 2011-10-20 13:54:13 America/New_York [NEW FEATURES] - Adds additional shorthand methods for all common HTTP verbs (HEAD, PUT, POST, DELETE) [David Golden] - post_form() method for POST-ing x-www-form-urlencoded data [David Golden] - www_form_urlencode() utility method [David Golden]
* Reimplement $[ as a moduleFather Chrysostomos2011-10-2126-28/+1337
| | | | | | | | | | | | | | | | | This commit reimplements $[ using PL_check hooks, custom pp func- tions and ties. Outside of its compile-time use, $[ is now parsed as a simple varia- ble, so function calls like foo($[) are permitted, which was not the case with the former implementation removed by e1dccc0. I consider that a bug fix. The ‘That use of $[ is unsupported’ errors are out of necessity deferred to run-time and implemented by a tied $[. Indices between 0 and the array base are now treated consistently, as are indices between a negative array base and zero. That, too, is a bug fix.
* perlrecharclass: NitKarl Williamson2011-10-201-1/+2
|
* Fix a path in the release guideFlorian Ragwitz2011-10-201-1/+1
|
* Create a perldelta for 5.15.5Florian Ragwitz2011-10-2011-365/+767
|
* Add the 5.15.4 epigraphFlorian Ragwitz2011-10-201-0/+10
|
* Add a release announcement template to PortingDavid Golden2011-10-203-0/+28
| | | | | | This makes it just a little bit easier for release managers and also fixes the perennial north-hemisphere bias in the future release date.
* Fix the installation of pod2htmlv5.15.4Florian Ragwitz2011-10-201-1/+1
|
* Add acknowledgements to the perldeltaFlorian Ragwitz2011-10-201-3/+25
|
* Stop Porting/acknowledgements.pl from producing hatespaceFlorian Ragwitz2011-10-201-4/+3
|
* Add 5.15.4 to perlhistFlorian Ragwitz2011-10-201-0/+1
|
* Remove the MANIFEST check from the release guideFlorian Ragwitz2011-10-202-16/+1
| | | | | | We already have porting tests catching this. I really don't see how this could end up being screwed or how it'd be more likely at this point during the release process than at any other time.
* Update Module::CoreList for 5.14.4Florian Ragwitz2011-10-203-3/+678
|
* Bump the perl version in various places for 5.15.4Florian Ragwitz2011-10-2021-140/+140
|
* Get perldelta into mostly finished stateFlorian Ragwitz2011-10-201-258/+4
|
* David changelogged thisFlorian Ragwitz2011-10-201-2/+0
| | | | Thanks, David!
* [perl #101738] Make sv_sethek set the UTF8 flag correctlyFather Chrysostomos2011-10-202-1/+12
| | | | | | | | | | | | | | | It was only ever turning it on, and not turning it off if the sv hap- pened to have it on from its previous use. This caused ref() (which uses sv_sethek(TARG,...)) to return a shared scalar with the UTF8 flag on, even if it was supposed to be off. For shared scalars, the UTF8 flag on ASCII strings does make a differ- ence. The pv *and* the flags are used in hash lookup, for speed. So a scalar returned by ref() with the UTF8 flag on by mistake would not work in hash lookups. exists $classes{ref $foo} would return false, even if there were an entry for that class.
View Lorry Controller Status