summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Implement the loop in tryAMAGICunDEREF_var() using while, rather than goto.Nicholas Clark2010-11-021-7/+7
| | | | | | | | Yes, it was a while loop implemented using goto, although this only became clear by untangling the macros. I believe it need never have been implemented as goto, given that the other user of tryAMAGICunW_var "broke" out of the "if"'s block using a return, hence that "if" could have been a "while" all along.
* Expand AMG_CALLun_var() into all its users, and eliminate it.Nicholas Clark2010-11-023-9/+10
| | | | | Aside from the 2 callers where it can be replaced with AMG_CALLun(). AMG_CALLun_var was only used in core.
* Inline tryAMAGICunW_var() into macros tryAMAGICun{DEREF_var,TARGET}Nicholas Clark2010-11-021-28/+36
| | | | | | | This also inlines and eliminates FORCE_SETs and setAGAIN. The three eliminated macros were not referenced from anywhere else. (The core, CPAN, code visible to Google codesearch.)
* Eliminate tryAMAGICunW() by refactoring tryAMAGICun{DEREF,TARGET}Nicholas Clark2010-11-021-4/+2
| | | | | tryAMAGICunW was only used within pp.h itself, and not referenced from anywhere else. (The core, CPAN, code visible to Google codesearch.)
* Remove unused AMAGIC macros from pp.h. Neither core nor CPAN uses any.Nicholas Clark2010-11-021-71/+0
| | | | | | | | | | | | | | | | | | | | Since commit 6f1401dc2acd2a2b, many AMAGIC macros in pp.h are no longer used in core, nor in modules or CPAN, nor in code visible to Google codesearch. Specifically: tryAMAGICbinW_var tryAMAGICbinW tryAMAGICbin_var tryAMAGICbin tryAMAGICbinSET tryAMAGICbinSET_var tryAMAGICbinW_var AMG_CALLbinL tryAMAGICun_var tryAMAGICun tryAMAGICunSET_var tryAMAGICunSET tryAMAGICftest
* Fix RT-70998: qq{\x{30ab}} =~ /\xab|\xa9/ produces warningscompileYves Orton2010-11-021-4/+10
|
* Add test for rt-70998: qq{\x{30ab}} =~ /\xab|\xa9/ produces warningsFather Chrysostomos2010-11-021-1/+38
|
* remove commit bit so that porting tests dont failYves Orton2010-11-020-0/+0
|
* Reorder struct xpvhv_aux to make two I32s adjacent.Nicholas Clark2010-11-021-1/+1
| | | | | | This avoids structure padding on architectures with 64 bit alignment for pointers. For example, on x86_64 it reduces the structure size from 48 to 40 bytes.
* Fix permissions on lib/overload/numbers.pm, accidentally changed by 0e244b13.Nicholas Clark2010-11-021-0/+0
|
* perldelta up to 7fd683ff3c3Father Chrysostomos2010-11-011-1/+17
| | | | I cheated by adding more commit IDs to the exception list.
* Increase DynaLoader’s versionFather Chrysostomos2010-11-011-1/+1
|
* Note changes to perlvar in perldeltabrian d foy2010-11-011-0/+5
|
* Whitespace fixes to perlvarbriandfoy/perlvarbrian d foy2010-11-011-3/+3
|
* Added ${^GLOBAL_PHASE} to perlvarbrian d foy2010-11-011-0/+64
|
* Fix some grammar nits thanks to jnarebbrian d foy2010-11-011-4/+3
|
* Added some missing index entries and fixed some whitespacebrian d foy2010-11-011-15/+19
|
* Get rid of spatial references 'above' and 'before' in perlvarbrian d foy2010-11-011-42/+42
| | | | | | We don't actually know where in space a formatter will put any text, or that the text will be there at all (e.g. perldoc -v)
* Use 'four' instead of 4 in body para in perlvarbrian d foy2010-11-011-1/+1
|
* Make $^V recommendation the first sentence in $]brian d foy2010-11-011-4/+6
|
* Add more English equivalents, index all names in perlvarbrian d foy2010-11-011-33/+46
|
* I think I have perlvar ordered and proper nowbrian d foy2010-11-011-339/+343
|
* Putting the variables in order, mostly, but not completely yetbrian d foy2010-11-011-286/+279
|
View Lorry Controller Status