summaryrefslogtreecommitdiff
path: root/pod/perlre.pod
Commit message (Collapse)AuthorAgeFilesLines
* Clarification in perlre.pod about captures created inside a DEFINEBrian Fraser2011-10-061-0/+13
|
* [perl #92898] Clarify (*THEN)’s scopeFather Chrysostomos2011-09-231-2/+4
|
* perlre: Note a bug's existenceKarl Williamson2011-09-221-0/+12
|
* Unicode::UCD: Make pod header consistentKarl Williamson2011-09-021-1/+1
| | | | | All the other function headers in this pod look like what this patch makes this one look like. Corresponding links to it are also revised.
* perlre: better /dual explanationKarl Williamson2011-07-281-63/+135
| | | | | | | | | This emphasized that the /dul modifiers should rarely be used explicitly, but are automatically selected when various pragma are in effect. It also calls the /a parameter ASCII-safe or ASCII-restrict instead of plain ASCII, as this is more accurate.
* perlre: NitsKarl Williamson2011-07-171-15/+17
|
* Trim multiple blank lines above =item in pod files.Nicholas Clark2011-06-221-1/+0
| | | | | | This makes many documents more consistent in their pod formatting. Don't trim blank lines between verbatim blocks and =item, as removing them makes the (raw) pod harder to read.
* perlre: Fix some line wrap issuesKarl Williamson2011-05-281-2/+2
| | | | | This fixes some verbatim text exceeding an 80 column window by shortening two =over amounts.
* perlre: Fix some line wrap issuesKarl Williamson2011-05-281-23/+24
| | | | | | This fixes some issues with the pod wrapping verbatim in 80 column windows by indenting less, and not having the comments so far to the right
* perlre: Change C<> to L<>Karl Williamson2011-05-281-1/+1
|
* Incorrect heading and index entries for (*MARK) in pod/perlre.podJohan Vromans2011-05-231-1/+1
|
* perlre: Fix broken linksKarl Williamson2011-05-191-2/+2
|
* [perl #90060] Fix location of (*COMMIT) in pod/perlre.podJohan Vromans2011-05-181-6/+6
| | | | | pod/perlre.pod: (*COMMIT) should be grouped under "Verbs without an argument".
* Doc changes for [perl #89750]Karl Williamson2011-05-031-1/+5
|
* perlre: Remove false statement about localesKarl Williamson2011-04-181-7/+2
|
* perlre: Nits in recently added textKarl Williamson2011-04-161-10/+11
|
* perlre.pod: ClarifyKarl Williamson2011-04-131-1/+19
| | | | | Several confusions have arisen about how things work, and this addresses them.
* perlre.pod: Update for 5.14Karl Williamson2011-04-121-74/+225
|
* [PATCH] [pod] improve documentation for (?(cond)yes|no)Moritz Lenz2011-03-191-1/+5
| | | | | | | | perlre: Include a high-level description of what it does, and what a missing pattern means perlreref: Include missing look-around cases Signed-off-by: Chris 'BinGOs' Williams <chris@bingosnet.co.uk>
* perlre clean-upFather Chrysostomos2011-03-091-69/+101
| | | | | | | | | | | | | | | Mostly typos, grammatical errors and factual errors (mostly due to bitrot), but also: • The section explaining how to work around the lack of look behind obviously has not been relevant for years. :-) • Since we have relative backreferences, we might as well use them in the explanation of the (?>...) construct. • Note that it’s possible to backtrack *past* (?>...), but not into it. • (?:non-zero-length|zero-length)* is *not* equivalent to nzl*|zl? as "aaaaab" =~ /(?:a|(?{print "hello"})(?=(b)))*/ demonstrates. • The custom re engine section doesn’t mention custom re engines. :-)
* Update docs for postfix /dual flagsFather Chrysostomos2011-02-201-86/+91
|
* Fix locale caseless matching and utf8Karl Williamson2011-02-191-3/+11
| | | | | | | As explained in the doc changes of this patch, under /l, caseless matching of code points less than 256 now use locale rules regardless of the utf8ness of the pattern or string. They now match the behavior of things like \w, in this regard.
* Fix bad pod links found by Test::Pod::LinkCheckApocalypse2011-02-151-2/+2
|
* perlre: Clarify (?(...)|)Father Chrysostomos2011-02-141-1/+6
| | | | | | • Mention look-around assertions in the list • It’s the code block’s return value, not the block itself that is used
* Add /aa regex modifierKarl Williamson2011-02-141-0/+3
| | | | Tests for \N{} with this option will be added later.
* Correctly list the allowed modifiers in the (?...) constructApocalypse2011-02-121-2/+2
|
* regex: \p{} in pattern implies Unicode semanticsKarl Williamson2011-01-271-9/+11
| | | | Now, a Unicode property match specified in the pattern will indicate that the pattern is meant for matching according to Unicode rules
* perlre.pod: Fix omission of /aKarl Williamson2011-01-271-1/+1
|
* [perl #82710] Fix incorrect pod link markup.Michael Stevens2011-01-241-1/+1
| | | | (found using code from Karl Williamson <public@khwilliamson.com>)
* [perl #82708] Fix unescaped chars in L<>.Michael Stevens2011-01-241-1/+1
|
* Add x-references in pods to new /a, etc.Karl Williamson2011-01-211-1/+6
|
* perlre.pod: corrections for /aKarl Williamson2011-01-181-11/+21
|
* Add /a regex modifierKarl Williamson2011-01-171-8/+18
| | | | | This restricts certain constructs, like \w, to matching in the ASCII range only.
* Nit in perlre.podKarl Williamson2010-12-011-1/+1
|
* Document Unicode doc fixKarl Williamson2010-12-011-19/+25
|
* DOCs: Clarify that \w matches marks and \PcKarl Williamson2010-10-311-1/+3
| | | | | | The previous documentation really didn't specify what \w is. It matches the underscore, but also all other connector punctuation, plus any marks, such as diacritical accents that occur within a word.
* Subject: [perl #58182] partial: Add uni \s,\w matchingKarl Williamson2010-10-151-3/+17
| | | | | | | | | | | | | | | | | | | This commit causes regex sequences \b, \s, and \w (and complements) to match in the latin1 range in the scope of feature 'unicode_strings' or with the /u regex modifier. It uses the previously unused flags field in the respective regnodes to indicate the type of matching, and in regexec.c, uses that to decide which of the handy.h macros to use, native or Latin1. I chose this for now rather than create new nodes for each type of match. An earlier version of this patch did that, and in every case the switch case: statements were adjacent, offering no performance advantage. If regexec were modified to use in-line functions or more macros for various short section of it, then it would be faster to have new nodes rather than using the flags field. But, using that field simplified things, as this change flies under the radar in a number of places where it would not if separate nodes were used.
* perlre.pod: slight rewordingKarl Williamson2010-10-151-4/+4
|
* Remove or update pod references to regexp reëntrance.Father Chrysostomos2010-10-131-6/+7
|
* Teach Perl about Unicode named character sequencesKarl Williamson2010-09-251-4/+4
| | | | | | | | | | | | | mktables is changed to process the Unicode named sequence file. charnames.pm is changed to cache the looked-up values in utf8. A new function, string_vianame is created that can handle named sequences, as the interface for vianame cannot. The subroutine lookup_name() is slightly refactored to do almost all of the common work for \N{} and the vianame routines. It now understands named sequences as created my mktables.. tests and documentation are added. In the randomized testing section, half use vianame() and half string_vianame().
* Add /d, /l, /u (infixed) regex modifiersKarl Williamson2010-09-221-17/+48
| | | | | | | | | | | | This patch adds recognition of these modifiers, with appropriate action for d and l. u does nothing useful yet. This allows for the interpolation of a regex into another one without losing the character set semantics that it was compiled with, as for the first time, the semantics is now specified in the stringification as one of these modifiers. To this end, it allocates an unused bit in the structures. The off- sets change so as to not disturb other bits.
* Add (?^...) regex constructKarl Williamson2010-09-201-3/+45
| | | | | | | | | | | | | | | | | | This adds (?^...) to signify to use the default regex modifiers for the cluster or embedded pattern-match modifier change. The major purpose of this is to simplify regex stringification, so that "^" is output in place of "-xism". As a result, the stringification will not change in the future when new regex modifiers are added, so tests, etc. that rely on a particular stringification will have to change now, but never again. Code that needs to work properly with both old- and new-style regexes can use something like the following: # Accept both old and new-style stringification my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism'; This construct is Ben Morrow's idea.
* RT #77150: perlre documentation issue and possible fixChas. Owens2010-08-141-5/+5
|
* pods: mention \o{}, 3 octal digitsKarl Williamson2010-07-191-5/+6
| | | | | | | | This patch adds a mention of \o{} to perlre to avoid the backreference ambiguities, and uses 3 octal digits in an example, and suggests using 3 digits where 2 were suggested before. Signed-off-by: David Golden <dagolden@cpan.org>
* Add \o{} escapeKarl Williamson2010-07-171-1/+1
| | | | | | | | | | This commit adds the new construct \o{} to express a character constant by its octal ordinal value, along with ancillary tests and documentation. A function to handle this is added to util.c, and it is called from the 3 parsing places it could occur. The function is a candidate for in-lining, though I doubt that it will ever be used frequently.
* perlre.pod: NitsKarl Williamson2010-07-171-6/+5
| | | | Signed-off-by: David Golden <dagolden@cpan.org>
* Add examples to perlre on perils of not using \g{}Karl Williamson2010-07-171-1/+16
| | | | | | These come from Abigail. Signed-off-by: David Golden <dagolden@cpan.org>
* perlre: Add heading to separate unrelated paragraphsKarl Williamson2010-06-281-0/+2
| | | | | | I don't know where the text for the stuff below this new heading should go, but it clearly doesn't belon with what came before, so add a heading to separate them, perhaps rearranging things later
* Prefer \g1 over \1 in podsKarl Williamson2010-06-281-58/+71
| | | | | | | \g was added to avoid ambiguities that \digit causes. This updates the pod documentation to use \g in examples, and to prefer it when explaining the concepts. Some non-symmetrical outlined text dealing with it was also cleaned up.
* Standardize on use of 'capture group' over 'buffer'Karl Williamson2010-06-281-53/+56
| | | | | | Both terms 'capture group' and 'capture buffer' are used in the documentation. This patch changes most uses of the latter to the former, as they are referenced using "\g".
View Lorry Controller Status