summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Initialize buffer to an empty string to avoid spurious uninitialized warningsRafael Garcia-Suarez2012-01-251-1/+1
|
* Update known_pod_issues.dat for x2p/psedChris 'BinGOs' Williams2012-01-251-0/+1
|
* Fix pod error in Unicode::UCDChris 'BinGOs' Williams2012-01-251-0/+1
|
* Update DB_File to CPAN version 1.826Chris 'BinGOs' Williams2012-01-255-5/+10
| | | | | | | | | [DELTA] 1.826 25 Jan 2012 * t/db-btree.t - fix use of "length @array" [RT ##74336]
* Revert "Regen known_pod_issues.dat"Chris 'BinGOs' Williams2012-01-251-11/+0
| | | | | | This reverts commit 5fa409a90f64110c5708f7141b376e9bdc54fbe2. Resolved by update of Pod-Parser to version 1.51
* Update Pod-Parser to CPAN version 1.51Chris 'BinGOs' Williams2012-01-2511-28/+11
| | | | | | | | | | | | | | | | [DELTA] 25-Jan-2012 Marek Rouchal <marekr@cpan.org> ----------------------------------------------------------------------------- Version 1.51 + CPAN#74271: Pod::Parser should not flag L<text|hyperlink> undo change CPAN#47473: L<alt text|URL> _is_ allowed (see discussion on pod-people and p5p); confirmed by blead change; references: http://code.activestate.com/lists/perl-pod-people/1690/ http://code.activestate.com/lists/perl-pod-people/1393/ http://perl5.git.perl.org/perl.git/commit/f6e963e4dd62b8e3c01b31f4a4dd57e47e104997 + bump all module versions (except Pod::PlainText) to 1.51 + update META.yml (thanks rjbs for the hint)
* Make the display of the warning "Useless use of a constant (%s)" more robustRafael Garcia-Suarez2012-01-253-26/+37
| | | | | | | | | | | | | If the constant is a string (POK), we dump it using pv_pretty, to properly escape non-printable characters. This also improves detection of utf-8 encoding in the constant to be printed. Also, this patch streamlines the tests for the type and value of that constant. Potential backwards-compatibility issues : if the constant is a string it will now be enclosed in double quotes, like this : Useless use of a constant ("a") in void context instead of Useless use of a constant (a) in void context
* CYG17 utf8 pathsReini Urban2012-01-241-34/+218
| | | | Use cygwin_conv_path since cygwin-1.7 and support native utf-8 paths.
* Update DB_File to CPAN version 1.825Chris 'BinGOs' Williams2012-01-247-7/+16
| | | | | | | | | | | [DELTA] 1.825 24 Jan 2012 * t/db-btree.t - fix use of "length @array" [RT ##74336] and [perl #108970]
* Increase $overload::VERSION to 1.18Father Chrysostomos2012-01-241-1/+1
|
* In overload::AddrRef, use ‘no overloading’Father Chrysostomos2012-01-241-11/+2
| | | | This speeds this up by about 13 times.
* [perl #108780] Make ‘no overloading’ work with qr//Father Chrysostomos2012-01-242-2/+18
| | | | | | | | | | | | | | Traditionally, overload::StrVal(qr//) has returned Regexp=SCALAR(0xc0ffee), and later Regexp=REGEXP(0xc0c0a) when regexps were made into first-class SVs. When the overloading pragma was added in 5.10.1, qr// things were not accounted for, so they would still stringify as (?-xism:) even with ‘no overloading’ (or as (?^:) under 5.14). This commit makes the overloading pragma work with qr// things, so that they stringify the same way as overload::StrVal; i.e., as Regexp=REGEXP(0xbe600d).
* Move amagic hint checking to new functionFather Chrysostomos2012-01-244-17/+29
| | | | so that stringification will be able to use it, too.
* Call FETCH once for stacked filetest opsFather Chrysostomos2012-01-242-2/+4
|
* skip sigdispatch.t on cygwin RT#88814Reini Urban2012-01-241-3/+5
|
* [perl #77388] Make stacked -t workFather Chrysostomos2012-01-237-100/+134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Up till now, -t was popping too much off the stack when stacked with other filetest operators. Since the special use of _ doesn’t apply to -t, we cannot simply have it use _ when stacked, but instead we pass the argument down from the previous op. To facilitate this, the whole stacked mechanism has to change. As before, in an expression like -r -w -x, -x and -w are flagged as ‘stacking’ ops (followed by another filetest), and -w and -r are flagged as stacked (preceded by another filetest). Stacking filetest ops no longer return a false value to the next op when a test fails, and stacked ops no longer check the truth of the value on the stack to determine whether to return early (if it’s false). The argument to the first filetest is now passed from one op to another. This is similar to the mechanism that overloaded objects were already using. Now it applies to any argument. Since it could be false, we cannot rely on the boolean value of the stack item. So, stacking ops, when they return false, now traverse the ->op_next pointers and find the op after the last stacked op. That op is returned to the runloop. This short-circuiting is proba- bly faster than calling every subsequent op (a separate function call for each). Filetest ops other than -t continue to use the last stat buffer when stacked, so the argument on the stack is ignored. But if the op is preceded by nothing other than -t (where preceded means on the right, since the ops are evaluated right-to-left), it *does* use the argument on the stack, since -t has not set the last stat buffer. The new OPpFT_AFTER_t flag indicates that a stacked op is preceded by nothing other than -t. In ‘-e -t foo’, the -e gets the flag, but not in ‘-e -t -r foo’, because -r will have saved the stat buffer, so -e can just use that.
* [rt.cpan.org #74289] Don’t make *CORE::foo read-onlyFather Chrysostomos2012-01-236-9/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | newATTRSUB requires the sub name to be passed to it wrapped up in a const op. Commit 8756617677dbd allowed it to accept a GV that way, since S_maybe_add_coresub (in gv.c) needed to pass it an existing GV not in the symbol table yet (to simplify code elsewhere). This had the inadvertent side-effect of making the GV read-only, since that’s what the check function for const ops does. Even if we were to call this a feature, it wouldn’t make sense as implemented, as GVs for non-ampable (&-able) subs like *CORE::chdir were not being made read-only. This commit adds a new flag to newATTRSUB, to allow a GV to be passed as the o parameter, instead of an op. While this may look as though it’s undoing the simplification in commit 8756617677dbd by adding more code, the new code is still conceptually simpler and more straightforward. Since newATTRSUB is in the API, I had to add a new _flags variant. (How did newATTRSUB get into the API to begin with?) In adding a test, I also discovered that ‘used once’ warnings were applying to these subs, which is obviously wrong. Commit 8756617677dbd caused that, too, as it was relying on the side-effect of newATTRSUB doing a GV lookup. This fixes that, too, by turning on the multi flag in S_maybe_add_coresub.
* Fix bad pointer size in has_trailing_nulEric Brine2012-01-231-2/+3
|
* point git-using installers to pod/perlgitRicardo Signes2012-01-231-0/+4
| | | | ...this change was promised to Jim Keenan
* perldelta for ~~ fixRicardo Signes2012-01-231-1/+2
|
* Enforce Any ~~ Object smartmatch precedenceLeon Timmermans2012-01-232-4/+2
|
* Increase $B::VERSION to 1.34Father Chrysostomos2012-01-231-1/+1
|
* B.xs add missing B::COP::stashflagsReini Urban2012-01-231-0/+11
| | | | Threaded perl added this field with 5.15.4 for utf8 stashes.
* B.pm POD: revise 44f7f2d5b1 on IoFLAGSReini Urban2012-01-231-2/+0
| | | | IoFLAGS are not defined in perliol.h
* More un-TODOs and two typos in vms/ext/filespec.t.Craig A. Berry2012-01-231-4/+4
| | | | | Two tests that actually pass under Extended Filename Syntax and two that will now pass if we give them the correct expectations.
* Handle directories with dots in fileify under EFS.Craig A. Berry2012-01-231-0/+14
| | | | | | | | | | When Extended Filename Syntax (EFS) is in effect, it's legal for directory names to contain dots that are not directory delimiters. This commit escapes such dots when they are part of the file portion of the fileified directory spec. This gets two more of the vms/ext/filespec.t tests passing when EFS is in effect.
* perlpodspec: Remove outdated textKarl Williamson2012-01-231-8/+0
| | | | | | | | | | | This warning against using alternate text with hyperlinks is no longer valid, See http://code.activestate.com/lists/perl-pod-people/1393/ And relevant changes: https://github.com/theory/pod-simple/commit/1e61e819debf9c7c23907d7bb9e37855665fd595 http://perl5.git.perl.org/perl.git/commit/f6e963e4dd62b8e3c01b31f4a4dd57e47e104997 https://github.com/theory/test-pod/commit/ae6a44894eda4fd09fb412d837efe543628cd7d6
* sv.c:sv_utf8_encode: simplify codeFather Chrysostomos2012-01-231-4/+1
| | | | sv_force_normal already croaks for read-only variables
* universal.c:XS_utf8_decode: rmv redundant codeFather Chrysostomos2012-01-231-1/+0
| | | | SvPV_force_nolen already calls sv_force_normal for us.
* Don’t allow read-only regexps to be tiedFather Chrysostomos2012-01-232-2/+12
| | | | | Since the test triggered another bug in freeing read-only regexps, this commit fixes that too.
* perldelta: Rmv git relict lineKarl Williamson2012-01-231-2/+0
| | | | | This line was a result of clearing a rebasing conflict, and I failed to remove it.
* sv_force_normal: Don’t confuse regexps with cowsFather Chrysostomos2012-01-223-3/+16
| | | | | Otherwise we get assertion failures and possibly corrupt string tables.
* English.pm: Remove fallacious commentFather Chrysostomos2012-01-221-1/+1
|
* Increase $English::VERSION to 1.05Father Chrysostomos2012-01-221-1/+1
|
* [perl #108794] Call special blocks in void contextFather Chrysostomos2012-01-222-2/+20
| | | | | Now BEGIN blocks, etc., are called in void context, so the result of evaluating the last statement is not wastefully copied.
* [rt.cpan.org #72767] Don’t propagate warnings into do-fileFather Chrysostomos2012-01-222-4/+27
| | | | | | I completely forgot about do-file when, in commit f45b078d2, I stopped eval from localising hints at run time. The result was that warning hints were propagating into do-file.
* Regen known_pod_issues.datChris 'BinGOs' Williams2012-01-222-0/+12
|
* Update Pod-Parser to CPAN version 1.50Chris 'BinGOs' Williams2012-01-2217-118/+280
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [DELTA] 16-Jan-2011 Marek Rouchal <marekr@cpan.org> ----------------------------------------------------------------------------- Version 1.50 + fix whitespace (esp. CR [\r] related) issues with different Perl versions on Windows (with Perl 5.8.8 [Activestate], and 5.6.1 [SUA]) + merge latest core (5.14.x) changes to this distro + CPAN#73446: fix minor POD error in InputObjects.pm + CPAN#43955: podchecker fails to detect superfluous =cut directive: implemented (and extended by a check for superfluous =pod commands) and documented in Pod::Checker; also added a note in the POD of all modules that they are part of the Pod::Parser distribution + CPAN#46695: use consistent version (1.50) for distribution and all Pod:: modules in this distro (except for Pod::PlainText, which stays at 2.05) + CPAN#52086: mismatch between distro and module version: same as above + CPAN#55121: correction for Pod::Find and t/pod/find.t on VMS + CPAN#47473: podchecker on L<> url with alt text ... causes an error in Pod::Checker now + CPAN#57954: Pod::Usage does not find perldoc when perl is relocatable ... use $Config{scriptdirexp} instead of scriptdir + CPAN#61223: podchecker notice missing blank line before command implemented with more tests in poderrs.t and self test of all *.pms + CPAN#66614: parse of no final newline vs perl -w ... a rare case, but fixed nevertheless + CPAN#68157: Pod-Parser-1.38/lib/Pod/Usage.pm question/bug ... pass through formatting options to Pod::Text + CPAN#70771: mishandles symbolic links in @INC ... fixed by making the paths in @INC absolute, using Cwd::abs_path() + CPAN#71139: 3 possible optimisations ... applied + several other rt.cpan.org tickets processed and closed
* Sync Module-CoreList version in Maintainers.plChris 'BinGOs' Williams2012-01-221-1/+1
|
* perllocale: Correct various Perl version referencesKarl Williamson2012-01-211-13/+13
| | | | Spotted by Nicholas Clark
* locale.t: White-space, comment onlyKarl Williamson2012-01-211-193/+194
| | | | | | | | This tidies up the white space to reflect a previous commit which added and subtracted blocks, and reflows to fit in an 80 column window, removes trailing white space, and rewords a comment. s
* Add :not_characters parameter to 'use locale'Karl Williamson2012-01-2114-179/+817
| | | | | This adds the parameter handling, tests, and documentation for this new feature which allows locale and Unicode to play well with each other.
* locale.t: Don't bother testing locales with malformed namesKarl Williamson2012-01-211-13/+14
| | | | Instead, just fail those.
* locale.t: remove unused debug stuffKarl Williamson2012-01-211-7/+0
|
* perluniintro: Shorten too-long verbatim linesKarl Williamson2012-01-212-4/+4
|
* perllocale: Remove trailing blanksKarl Williamson2012-01-211-8/+8
|
* locale.pm: Pod tweaksKarl Williamson2012-01-211-6/+7
|
* regexp.h: Update commentKarl Williamson2012-01-211-3/+4
|
* perllocale: Add caveat on UTF-8 localesKarl Williamson2012-01-211-4/+11
| | | | | | It turns out that the C library may not handle UTF-8 locales properly, and the docs should mention that instead of blindly encouraging their use.
* op.c: Call macro instead of using explicit bitKarl Williamson2012-01-211-2/+2
| | | | The macro hides the bit name.
View Lorry Controller Status