summaryrefslogtreecommitdiff
path: root/pod
Commit message (Collapse)AuthorAgeFilesLines
* mktables: In-line defns for tables up to 3 rangesKarl Williamson2014-03-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | eb0925341cc65ce6ce57503ec0ab97cdad39dc98 caused the definitions for about 45% of the Unicode tables to be placed in-line in Heavy.pl instead of them having to be read-in from disk. This new commit extends that so that about 55% are in-lined, by in-lining tables which consist of up to 3 ranges. This is a no-brainer to do, as the memory usage does not increase by doing it, and disk accesses go down. I used the delta in the disk size of Heavy.pl as a proxy for the delta in the memory size that it uses, as what this commit does is to change various scalar strings in it. Doing this measurement indicates that this commit results in a slightly smaller Heavy.pl than what was there before eb092534. The amounts will vary between Unicode releases. I also checked for Unicode beta 7.0, and the sizes are again comparable, with a slightly larger Heavy.pl for the 3-range version there. For 4-, 5-, ... range tables, doing this results in slowly increasing Heavy.pl size (and hence more and more memory use), and that is something we may wish to look at in the future, trading memory for fewer files and less disk start-up cost. But for the imminent v5.20, doing it for 3-range tables doesn't cost us anything, and gains us fewer disk files and accesses.
* replace links to perllexwarn with links to warningsRicardo Signes2014-03-185-7/+7
| | | | or, sometimes, simply remove them
* turn perllexwarn into a stubRicardo Signes2014-03-181-595/+4
|
* perlfunc: clarify kill()'s return valueDavid Mitchell2014-03-171-3/+4
|
* RT #121230, tests for process group kill on Win32Daniel Dragan2014-03-171-2/+7
| | | | | | | Add tests for 111f73b5d79, the fix for kill -SIG on win32, which was broken in 5.18.0 (A follow-up commit will clean this code up a bit)
* Update perldelta for core changes to this pointAaron Crane2014-03-151-3/+59
| | | | This doesn't include module version updates.
* perlfunc: layout getpw*&c return values as a tableAristotle Pagaltzis2014-03-111-7/+9
|
* perldiag: Clarify that lexicals do not trigger "used only once"Aristotle Pagaltzis2014-03-101-3/+5
|
* It is and always will be safe to delete the most recent key returned from each.Paul Johnson2014-03-101-3/+2
|
* Upgrade CPAN::Meta from version 2.140630 to 2.140640Steve Hay2014-03-061-1/+1
|
* note that the ~~ operator is experimentalRicardo Signes2014-03-051-1/+3
| | | | (cherry picked from commit 43c6e0a7ba1950c4a64b59be5d0a9cd7b1807cca)
* Upgrade Locale-Codes from version 3.29 to 3.30Steve Hay2014-03-051-0/+6
|
* Upgrade Parse-CPAN-Meta from version 1.4413 to 1.4414Steve Hay2014-03-051-0/+8
|
* Upgrade CPAN-Meta from version 2.133380 to 2.140630Steve Hay2014-03-051-0/+6
|
* Describe the improvements to make_ext.pl in perldelta.Nicholas Clark2014-03-021-1/+5
|
* fix RT #121299 - Inconsistent behavior with backreferences nested inside ↵Yves Orton2014-02-241-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | subpattern references Match variables should be dynamically scoped during GOSUB and GOSTART. The callers state should be inherited by the callee, but once the callee returns, the callers state should be restored. This is different from EVAL, where the callers and callees state are expected to not be the same (although might be the same), and where the "reasonable" match semantics differ. Currently the following two one liners will produce different results: $ ./perl -Ilib -le'"<ab><>>" =~/ < (?: \1 | [ab]+ ) (>) (?0)? /x and print $&;' <ab><>> $ ./perl -Ilib -le'$qr= qr/ < (?: \1 | [ab]+ ) (>) (??{ $qr })? /x; "<ab><>>" =~ m/$qr/ and print $&;' <ab> While I think reasonable people could argue that we should special case things when we know that the return from (??{ ... }) is the same as the currently executing pattern I think explaining the difference would be harder than necessary. On the contrary making GOSUB/GOSTART exactly the same as EVAL, so that the match vars were totally independent seems to throw away an opportunity for much more powerful semantics than can be offered by EVAL.
* Upgrade HTTP-Tiny from version 0.042 to 0.043Steve Hay2014-02-211-0/+7
|
* perldelta for 257518b902Tony Cook2014-02-211-0/+7
|
* perldelta for 3e63bed3c5, 58572ed82fTony Cook2014-02-211-2/+5
|
* Restore proper functioning of -MdiagnosticsKarl Williamson2014-02-202-2/+2
| | | | | | | | Commit 1c604e7c7f fixed some pod errors, but broke ./perl -Ilib -Mdiagnostics -e '$/=[]' This fixes that.
* Change 'semantics' to 'rules'Karl Williamson2014-02-207-28/+28
| | | | | | The term 'semantics' in documentation when applied to character sets is changed to 'rules' as being a shorter less-jargony synonym in this case. This was discussed several releases ago, but I didn't get around to it.
* Fix pod typo (kentnl++)Peter Rabbitson2014-02-201-1/+1
|
* bump to version 5.19.10 and fix the version number reference in op.cTony Cook2014-02-201-1/+1
|
* new perldelta for 5.19.10Tony Cook2014-02-204-543/+960
|
* note lib/locale.t rare failurev5.19.9Tony Cook2014-02-201-0/+10
|
* update perlhist for 5.19.9Tony Cook2014-02-201-0/+1
|
* finalize perldelta for 5.19.9Tony Cook2014-02-201-231/+93
|
* Make taint checking regex compile time instead of runtimeKarl Williamson2014-02-192-15/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | See discussion at https://rt.perl.org/Ticket/Display.html?id=120675 There are several unresolved items in this discussion, but we did agree that tainting should be dependent only on the regex pattern, and not the particular input string being matched against: "The bottom line is we are moving to the policy that tainting is based on the operation being in locale, without regard to the particular operand's contents passed this time to the operation. This means simpler core code and more consistent tainting results. And it lessens the likelihood that there are paths in the core that should taint but don't" This commit does the minimal work to change regex pattern matching to determine tainting at pattern compilation time. Simply put, if a pattern contains a regnode whose match/not match depends on the run-time locale, any attempt to match against that pattern will taint, regardless of the actual target string or runtime locale in effect. Given this change, there are optimizations that can be made to avoid runtime work, but these are deferred until later. Note that just because a regular expression is compiled under locale doesn't mean that the generated pattern will be tainted. It depends on the actual pattern. For example, the pattern /(.)/ doesn't taint because it will match exactly one character of the input, regardless of locale settings.
* perllocale: Add note about ENVIRONMENT variableKarl Williamson2014-02-191-0/+9
| | | | | This variable is part of the environment, but wasn't previously mentioned.
* perlsec: NitKarl Williamson2014-02-191-2/+3
|
* Update Config::Perl::V to 0.20H.Merijn Brand2014-02-191-0/+6
|
* perlootut: replace Object::Tiny with Class::TinyDavid Golden2014-02-191-11/+13
| | | | | | | | | Class::Tiny is similarly small and simple in API, but with more powerful features available. Comparison to Object::Tiny and Class::Accessor is here: https://metacpan.org/pod/Class::Tiny#RATIONALE At mst's suggestion, a link to Class::Tiny::Antlers for Moose-syntax is included.
* perldelta updatesTony Cook2014-02-191-1/+10
|
* perlvar.pod: suggest string comparisons for $]David Golden2014-02-181-2/+2
|
* Fix pod errorsKarl Williamson2014-02-182-2/+2
|
* re-import 5.19.8 delta form 5.19.8Ricardo Signes2014-02-181-1/+503
|
* update perlport with currently unresolved Cygwin test failuresTony Cook2014-02-181-0/+19
|
* Update Parse-CPAN-Meta to CPAN version 1.4413Tony Cook2014-02-181-1/+1
| | | | | | | | | 1.4413 2014-02-17 20:04:23-05:00 America/New_York [FIXED] - UTF-8 decoding is done differently to avoid requiring a newer version of Encode (Graham Knop)
* perldelta updatesTony Cook2014-02-181-0/+42
|
* Upgrade Digest-SHA from 5.86 to 5.87Steve Hay2014-02-181-2/+4
|
* Clarify distinction between contents of dist/ and ext/.James E Keenan2014-02-171-8/+13
| | | | | | Amended with a suggestion from rjbs. For: RT #120808
* perllocale: Corrections and nitsKarl Williamson2014-02-151-12/+23
|
* perlfunc: NitKarl Williamson2014-02-151-2/+2
|
* Revert "Free up bit for regex ANYOF nodes"Karl Williamson2014-02-151-190/+137
| | | | | This reverts commit 34fdef848b1687b91892ba55e9e0c3430e0770f6, and adds comments referring to it, in case it is ever needed.
* Free up bit for regex ANYOF nodesKarl Williamson2014-02-151-137/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | This commit frees up a bit by using an extra regnode to pass the information to the regex engine instead of the flag. I originally thought that if this was needed, it should be the ANYOF_ABOVE_LATIN1_ALL bit, as that might speed some things up. But if we need to do this again by adding another node to get another bit, we want one that is mutually exclusive of the first one we did, For otherwise we start having to make 3 nodes instead of two to get the combinations: 1 0 0 1 1 1 This combinatorial problem is avoided by using bits that are mutually exclusive, which the ABOVE_LATIN1_ALL isn't, but the one freed by this commit ANYOF_NON_UTF8_NON_ASCII_ALL is only set under /d matching, and there are other bits that are set only under /l, so if we need to do this again, we should use one of those. I wrote this code when I thought I really needed a bit. But since, I have figured out a better way to get the bit needed now. But I don't want to lose this code to posterity, so this commit is being made long enough to get the commit number, then it will be reverted, adding comments referring to the commit number, so that it can easily be reconstructed when necessary.
* alphabetise perldiagFather Chrysostomos2014-02-151-5/+5
|
* Deprecate uses of POSIX::isfoo()Karl Williamson2014-02-153-1/+18
| | | | | | | | | | | These functions have been supplanted in more modern Perls by /[[:posix:]]/. The documentation has been wrong; they don't handle UTF-8 and return true on an empty string. Rather than try to fix them, the decision has been made to deprecate them instead. See http://markmail.org/thread/jhqcag5njmx7jpyu This commit also updates the documentation to be accurate.
* Improve fallback during locale initializationKarl Williamson2014-02-152-9/+31
| | | | | | | | | | | | | If Perl encounters a problem during startup trying to initialize the locales from the environment it has immediately reverted to the "C" locale. This commit generalizes that so it tries each of the applicable environment variables in order of priority until it works, or it gives up and uses the "C" locale. For example, if LC_ALL is set to something that is invalid, but LANG is valid, LANG will be used. This was motivated by trying to get the Windows system default locale used in preference to "C" if all else fails.
* Emulate POSIX locale setting on WindowsKarl Williamson2014-02-152-1/+8
| | | | | | | | | | | | | Locale initialization and setting on Windows haven't been as described in perllocale for setting locales to "". This is because that tells Windows to use the system default locale, as set through the Control Panel, but on POSIX systems, it means to look at various environment variables. This commit creates a wrapper for setlocale, used only on Windows, that looks for the appropriate environment variables when called with a "" input locale. If none are found, it continues to use the system default locale.
* perldelta updatesTony Cook2014-02-141-0/+65
|
View Lorry Controller Status