summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update File-Fetch to CPAN version 0.26Chris 'BinGOs' Williams2010-11-074-7/+99
| | | | | | | | | [DELTA] Changes for 0.26 Sat Nov 6 23:30:59 2010 ================================================= * Added support for HTTP::Lite * Resolved issue with '-l' switch and iosock fetch
* Fix a compiler warningFlorian Ragwitz2010-11-061-1/+1
| | | | | | gcc said: regexec.c: In function ‘S_reginclass’: regexec.c:6305: warning: suggest parentheses around ‘&&’ within ‘||’
* localize $@ during binmode (RT#78844)David Golden2010-11-062-1/+3
|
* Add Nicolas Kaiser to AUTHORS.Craig A. Berry2010-11-061-0/+1
|
* RT 78836: vms/vms.c: dubious expressionsNicolas Kaiser2010-11-061-2/+2
| | | | | | I noticed two dubious expressions that look as if they were intended to be assignments. The comment above the code says it's broken.
* Add new ops in Opcode, so it does not warn at compilationRafael Garcia-Suarez2010-11-061-3/+3
| | | | The ops are the recently-introduced reach, rvalues, rkeys and transr.
* G_VOID, G_SCALAR, and G_ARRAY are not separate bits anymoreNiko Tyni2010-11-062-5/+13
| | | | | | | | Commit 2f8edad0d37e91319b6ba10b3745327ea49c179 made G_ARRAY equal to G_SCALAR | G_VOID, contrary to perlcall.pod. Bring the documentation up to date and add a test to prevent a similar (although unlikely) accident in the future.
* Added test for RT#78844David Golden2010-11-061-1/+9
|
* Eliminate a few more $op->private calls in DeparseFather Chrysostomos2010-11-061-4/+4
|
* Make Deparse work with y/å/ø/Father Chrysostomos2010-11-062-2/+9
|
* Test y///r with B::DeparseFather Chrysostomos2010-11-061-1/+4
|
* Avoid a run-time miniperl check every time SWASHNEW is calledFather Chrysostomos2010-11-051-1/+7
|
* Remove details that changed over seven years ago.Tom Hukins2010-11-051-8/+0
| | | | | FreeBSD 5.0 was released on 2003-01-17 so everyone should be used to FreeBSD lacking Perl in its base system by now.
* Clarify wording.Tom Hukins2010-11-051-2/+2
|
* Refer to other documents more specificallyTom Hukins2010-11-051-1/+2
|
* Link to perlbug's PODTom Hukins2010-11-055-5/+5
|
* utf8_heavy.pl: Make callable during Perl's compilationKarl Williamson2010-11-051-3/+16
| | | | | | | | | | | | | | | It's possible for this to be called during the compilation phase of Perl by miniperl before the Unicode tables have been built. This patch checks if dynamic loading is available, and if not evals the require needed to gain access to the tables. If it succeeds, the tables have been built; if it doesn't, instead of dying, just return empty tables, as currently the things being built don't require information outside the ASCII range, which is hard-coded into Perl without needing the tables. In the future, that may not be the case, and then likely the tables will have to be shipped with Perl, and make regen would be done to rebuild them.
* A hack for t/harness to restore the ability to run tests listed in @ARGVNicholas Clark2010-11-051-1/+4
|
* Tweak the test from 98517ccb8d5e8751 to work with PERL_UNICODE set.Nicholas Clark2010-11-051-2/+2
| | | | | | One should always generate the golden B::Concise output with PERL_UNICODE set so that ${^OPEN} is set, as the test system knows how to take it out, not put it in.
* Document that the -Ci, -Co, and -CD options have file scopeNiko Tyni2010-11-052-6/+21
| | | | | | While the other -C settings are global, "i" and "o" only affect subsequent open() calls in the current file. Document this and add two tests to make sure the documented behaviour doesn't change accidentally.
* Avoid creating lots of mortals in B::walkoptree()Nicholas Clark2010-11-052-17/+53
| | | | | | | | | | | When calling out to the user-supplied method, re-use the same reference and object where possible. Only create a new one if the user supplied method modified the reference or object passed to it. The previous implementation had a comment "Use the same opsv. Rely on methods not to mess it up." but it was actually generating a new reference for every call, and also a new object for every recursive call. So massive churn of objects, and large accumulation of mortals on the temp stack.
* B::Concise was failing to traverse some children of PMOPsNicholas Clark2010-11-052-4/+28
| | | | | | | | Notably the substcont of s/// was being missed. The bug was introduced as part of c0939ceec1b3e902, "Re: [patch] teach B::Concise to see XS code", which did rather more than it said on the tin.
* Stop B from crashing on y/å/ø/Father Chrysostomos2010-11-042-1/+11
|
* RT 78818 Sync the description of \E in perlop with perlrebrian d foy2010-11-041-1/+1
| | | | | | | | | | Posted by Niko Tyni Commit 9bb1f947 fixed the description of \E in perlre.pod to include the 'end quoted section' functionality, so update the similar list in perlop.pod too. Triggered by http://bugs.debian.org/126238
* RT 78814 perlfunc/open(): four items are not a triplebrian d foy2010-11-041-2/+2
| | | | | | | | | | | | | Reported by Niko Tyni Commit b76cc8ba45957 made each group a quadruple without updating the name. Take out the name altogether to avoid this in the future. Also update the reference to "list form" pipes to include both the old last example and the new one. Originally noticed by Reuben Thomas in http://bugs.debian.org/469402
* Some tests for B::walkoptree.Nicholas Clark2010-11-043-0/+62
| | | | | Quite likely coverage isn't that good, but some tests are better than none. More tests welcome.
* Create &B::{IV,PV}::as_string using typeglob assignment rather than goto &Nicholas Clark2010-11-041-2/+2
| | | | | Typeglob assignment avoids compiler work creating the optree for a second subroutine, and runtime work executing that optree.
* Exclude more exported but non-existent functions.Craig A. Berry2010-11-041-3/+18
| | | | | | | | | | | pp_reach, pp_rvalues, and pp_transr are aliases, but regen/opcode.pl generates declarations for aliases as if they were C functions in their own right. This is necessary for aliases that refer to mathoms (as most of them do) but seems less right for new entries that will never refer to an actual function of the same name. For now, these need to be explicitly excluded when building the linker options file on VMS. Failure to do so breaks the build with undefined symbol warnings.
* Update version of Safe in Maintainers.pl to match recent version changeChris 'BinGOs' Williams2010-11-041-1/+1
|
* Avoid needing to stub B::OPf_KIDS by loading the XS earlier.Nicholas Clark2010-11-041-19/+25
| | | | | | | | This will also inline the constant in the code of walkoptree_slow(). Things are complicated by the fact that B's BOOT code needs $VERSION set, and pushes to @EXPORT_OK. Move the 'use strict' much earlier.
* Remove two use of dXSI32; superfluous because xsubpp automatically adds it.Nicholas Clark2010-11-042-3/+0
|
* Add Marty Pauley’s other e-mail address to checkAUTHORS.plFather Chrysostomos2010-11-041-0/+1
|
* fix for #23790.Marty Pauley2010-11-042-3/+32
| | | | | | | padav is leaving an arrayref on the stack when producing the return value for an lvalue sub. But when this is in an argument list it really should be a array, not a ref. So, in leavesublv I check for this case and expand the arrayref to an array.
* Inline tryAMAGICunDEREF_var() into its callers and eliminate it.Nicholas Clark2010-11-034-11/+15
| | | | Nothing outside the core was using this macro.
* Add Perl_amagic_deref_call() to implement the bulk of tryAMAGICunDEREF_var().Nicholas Clark2010-11-038-25/+35
| | | | | | | | | This removes around 300 bytes of object code from each place it was previously inlined. It also provides a better interface - quite a lot of the core currently bodges things by creating a local variable C<SV **sp = &sv> to use the macro. Change the XS::APItest wrapper to amagic_deref_call().
* Add tests for tryAMAGICunDEREF_var().Nicholas Clark2010-11-035-10/+118
|
* Update Unicode-Collate to CPAN version 0.65Chris 'BinGOs' Williams2010-11-0322-29/+8659
| | | | | | | | | | | | [DELTA] 0.65 Wed Nov 3 13:10:20 2010 - U::C::Locale newly supports locale: zh and its some variants. (zh__big5han, zh__gb2312han, zh__pinyin, zh__stroke) - added Unicode::Collate::CJK::Big5 for zh__big5han. - added Unicode::Collate::CJK::GB2312 for zh__gb2312han. - added Unicode::Collate::CJK::Pinyin for zh__pinyin. - added Unicode::Collate::CJK::Stroke for zh__stroke.
* fix 68564: /g failure with zero-width patternsYves Orton2010-11-032-5/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is based on a patch by Father Chrysostomos <sprout@cpan.org> The start class optimisation has two modes, "try every valid start position" (doevery) and "flip flop mode" (!doevery) where it trys only the first valid start position in a sequence. Consider /(\d+)X/ and the string "123456Y", now we know that if we fail to match X after matching "123456" then we will also fail to match after "23456" (assuming no evil tricks are in place, which disable the optimisation anyway), so we know we can skip forward until the check /fails/ and only then start looking for a real match. This is flip-flop mode. Now consider the case with zero-width lookahead under /g: /(?=(\d+)X)/. In this case we have an additional failure mode, that is failure when we match a zero-width string twice at the same pos(). So now, the "flip-flop" logic breaks as it /is/ possible that we could match at "23456" when we couldn't match at "123456" because of the zero-length twice at the same pos() rule. For instance: print $1 for "123"=~/(?=(\d+))/g should first match "123". Since $& is zero length, pos() is not incremented. We then match again, successfully, except that the match is rejected despite technical-success because its $& is also zero length and pos() has not advanced. If the flip-flop mode is enabled we wont retry until we find a failing character first. The point here is that it makes perfect sense to disable the "flip-flop" mode optimisation when the start class is inside a lookahead as it really doesnt apply.
* clarify code and intent of code in a commentYves Orton2010-11-031-3/+9
|
* fix incorrect commentYves Orton2010-11-031-1/+1
|
* fix the trie part of rt-78356Yves Orton2010-11-032-1/+3
| | | | | | When the jump code was added the case of an empty string followed by a jump wasnt accounted for. One could argue it should not happen however that is a matter for a different commit.
* Document y///rFather Chrysostomos2010-11-021-6/+23
|
* Document the ‘Using !~’ errorsFather Chrysostomos2010-11-021-0/+7
|
* Increase B::Concise’s versionFather Chrysostomos2010-11-021-1/+1
|
* y///rFather Chrysostomos2010-11-027-16/+67
|
* s///r leaks like a sieveFather Chrysostomos2010-11-022-2/+7
|
* Don’t capitalise words in the middle of an error messageFather Chrysostomos2010-11-022-2/+2
|
* Add transr op typeFather Chrysostomos2010-11-026-3/+18
| | | | | for the upcoming y///r feature. There are not enough flag bits, hence the extra type.
* Avoid multiple $op->private calls in B::Deaprse::pp_transFather Chrysostomos2010-11-021-3/+4
|
* Inline RvDEEPCP() into its only caller, Perl_amagic_call().Nicholas Clark2010-11-022-13/+9
| | | | | | | Only Perl_amagic_call() was using RvDEEPCP() when it was added in 5.000, and I believe that it's never had any other users (in the core, on CPAN, or anywhere else visible to Google codesearch). Hence it seems an ideal candidates to be inlined and eliminated.
View Lorry Controller Status