summaryrefslogtreecommitdiff
path: root/pod/perlop.pod
Commit message (Collapse)AuthorAgeFilesLines
* perlop: Mention the s///le special caseFather Chrysostomos2011-03-131-0/+8
| | | | | This is apparently undocumented except in perldiag and a previous perldelta.
* Update docs for postfix /dual flagsFather Chrysostomos2011-02-201-11/+12
|
* perlop.pod: Update to account for /rKarl Williamson2011-02-191-1/+2
|
* multifile patch against blead/pod/*.podTom Christiansen2011-02-151-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | I mostly fixed spelling mistakes, some of very long standing, but a few files got more attentive word-smithying. I've updated: pod/perl.pod pod/perldelta.pod pod/perl592delta.pod pod/perl5120delta.pod pod/perl51310delta.pod pod/perl5139delta.pod pod/perlfunc.pod pod/perlop.pod pod/perlrebackslash.pod pod/perlrecharclass.pod pod/perlutil.pod pod/perlhack.pod pod/perlintern.pod pod/perlnetware.pod pod/perlpolicy.pod
* Fix up \cX for 5.14Karl Williamson2011-02-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | Throughout 5.13 there was temporary code to deprecate and forbid certain values of X following a \c in qq strings. This patch fixes this to the final 5.14 semantics. These are: 1) a utf8 non-ASCII character will croak. This is the same behavior as pre-5.13, but it gives a correct error message, rather than the malformed utf8 message previously. 2) \c{ and \cX where X is above ASCII will generate a deprecated message. The intent is to remove these capabilities in 5.16. The original agreement was to croak on above ASCII, but that does violate our stability policy, so I'm deprecating it instead. 3) A non-deprecated warning is generated for all other \cX; this is the same as throughout the 5.13 series. I did not have the tuits to use \c{} as I had planned in 5.14, but \N{} can be used instead.
* Add x-references in pods to new /a, etc.Karl Williamson2011-01-211-0/+7
|
* Typos and nits in podsKarl Williamson2011-01-191-1/+1
|
* minor amendment to documentation of ?PATTERN?David Golden2010-11-241-1/+3
|
* Deprecate ?PATTERN? without explicit m operatorZefram2010-11-241-12/+17
| | | | | | | | | | Deprecate ?PATTERN?, recommending the equivalent m?PATTERN? syntax, in order to eventually allow the question mark to be used in new operators that would currently be ambiguous. (With minor reconciliation edits by David Golden) Signed-off-by: David Golden <dagolden@cpan.org>
* Clarify m?PATTERN? is ok and only ?PATTERN? is notDavid Golden2010-11-241-12/+12
|
* Spelling/grammar nitsRafael Garcia-Suarez2010-11-171-2/+2
|
* Doc fix for [perl #78642] Logical defined or not equivalent to ternary ↵Rafael Garcia-Suarez2010-11-151-4/+5
| | | | | | operator with defined The ternary operator can be used in lvalue context; $a // $b cannot.
* 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
* Document y///rFather Chrysostomos2010-11-021-6/+23
|
* Defer to perlfunc on \G and pos()brian d foy2010-10-281-13/+15
|
* Improve documentation of \QEric Brine2010-10-121-4/+18
|
* perlop.pod: Clarify -’s string/number distinctionFather Chrysostomos2010-10-041-5/+6
|
* [perl #22193] Clarify references to ‘use integer’ in perlopCasey West2010-09-281-7/+7
|
* Teach Perl about Unicode named character sequencesKarl Williamson2010-09-251-2/+2
| | | | | | | | | | | | | 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().
* * Fixed output for lex-like scanners example in perlopbrian d foy2010-09-231-4/+4
| | | | | This should probably be given-when instead of a naked block and a redo
* Fix /[\8]/ to not match NULL; give correct warningKarl Williamson2010-09-161-3/+0
| | | | | | | | | | 8 and 9 are not treated as alphas in parsing as opposed to illegal octals. This also adds tests to verify that 1-3 digits work in char classes. I created an isOCTAL macro in case that lookup gets moved to a bit field, as I plan to do later, for speed.
* perlop.pod: Reword escapes that have ordinalsKarl Williamson2010-07-261-49/+59
|
* perlop.pod: document \o{} escapeDavid Golden2010-07-171-16/+30
| | | | This is a merge resolution based on original work by Karl Williamson.
* perlop.pod: Rephrase hexadecimal escape wordingDavid Golden2010-07-161-25/+61
| | | | | | | Clarifies how hexadecimal escapes are interpreted, with particular attention to the treatment of invalid characters. Based on an original draft patch by Karl Williamson.
* perlop.pod: Document current \000 \x behaviorKarl Williamson2010-07-131-21/+58
| | | | Signed-off-by: David Golden <dagolden@cpan.org>
* Fix typoAbigail2010-07-081-1/+1
|
* Rephrase perlop for non-destructive substitutionDavid Golden2010-05-221-6/+6
|
* Add s///r (non-destructive substitution).David Caldwell2010-05-221-6/+26
| | | | | | | | | | | | | | | | This changes s/// so that it doesn't act destructively on its target. Instead it returns the result of the substitution (or the original string if there was no match). In addition this patch: * Adds a new warning when s///r happens in void context. * Adds a error when you try to use s///r with !~ * Makes it so constant strings can be bound to s///r with =~ * Adds documentation. * Adds some tests. * Updates various debug code so it knows about the /r flag. * Adds some new 'r' words to B::Deparse.
* PATCH: Clean up EBCDIC handling of \cXKarl Williamson2010-05-171-3/+3
| | | | | | | | | | The function perl_ebcdic_control() is unnecessary, as the toCTRL macro that calls it can be changed to just map EBCDIC to ASCII first, and then doing the normal procedure. This means that EBCDIC and ASCII will no longer diverge. Currently, EBCIDIC gives a syntax error for inputs outside its domain, whereas the ASCII version accepts some of them.
* Fix to display ok in 80 columnsKarl Williamson2010-05-081-24/+25
|
* Clarify \c in perlop.pod.Karl Williamson2010-04-261-24/+61
| | | | And structure the table containing \c better.
* [perl #74198] Typo in perlop(1)Rafael Garcia-Suarez2010-04-131-2/+2
| | | | reported by rrt@sc3d.org
* Document parsing changes for [perl #56444] patchKarl Williamson2010-02-281-0/+5
|
* Document \N{U+...}Karl Williamson2010-02-281-5/+10
|
* * Fill out the docs on the yada to show it as a satand in for statements, ↵brian d foy2010-01-281-10/+57
| | | | not expressions
* * Note that the flip-flop operator maintains state across subroutine callsbrian d foy2010-01-261-17/+17
|
* * Em dash cleanup in pod/brian d foy2010-01-131-4/+4
| | | | | | | | | | | | | I looked at all the instances of spaces around -- and in most cases converted the sentences to use more appropriate punctuation. In general, the -- in the perl docs seem to be there only to make really complicated and really long sentences. I didn't look at the closed em-dashes. They probably have the same sentence-complexity problem. I left some open em-dashes in place. Those are the ones used in lists.
* * fix a perlop fix from debian: http://bugs.debian.org/514814brian d foy2009-12-271-2/+2
| | | | | | | | | | | | | | | | | The original said C<< <I<filehandle>> >> The italic is probably meant for "filehandle", which is a stand-in for a concrete filehandle. The italic should not apply to the syntax for the line input operator. The fix turned it inside out and brought back the ugly interior sequences: I< C< E<lt>filehandleE<gt> > > It's much better without worrying about the italic face.
* Pod formatting fixJosh ben Jore2009-09-291-1/+1
|
* Pod formatting fixRoberto C. S�nchez2009-09-291-1/+1
| | | | Signed-off-by: Josh ben Jore <jjore@cpan.org>
* Use alternative URLs for links which are now broken (link rot)Leon Brocard2009-09-041-1/+1
|
* Document better what is allowed as regex delimitersDavid Nicol2009-08-301-8/+10
| | | | Identifier characters are allowed. Also add a test
* Removed '...' ellipses from docs about '...' flip-flop operatorKen Williams2009-08-111-4/+4
|
* Remove !!! and ??? operatorsRafael Garcia-Suarez2009-07-221-24/+5
| | | | | Those were adding non backwards compatible syntax, unlike "...", as pointed out in bug #67646.
* Revised description of => operatorIan Goodacre2009-06-091-7/+11
| | | | | | Provided more explicit description of the words that are handled specially by the => operator and removed the incorrect description of how other expressions are handled.
* Re: [PATCH] [doc] be more explicit about magic argvMoritz Lenz2008-10-301-0/+12
| | | | | Message-ID: <20081030182902.25398.qmail@lists.develooper.com> p4raw-id: //depot/perl@34670
* Fix typo in perlop.podJerry D. Hedden2008-05-191-1/+1
| | | | | | From: "Jerry D. Hedden" <jdhedden@cpan.org> Message-ID: <1ff86f510805190858v4a7f6e06k5f949ff31384137d@mail.gmail.com> p4raw-id: //depot/perl@33870
* Add ..., !!!, and ??? operatorschromatic2008-05-181-1/+34
| | | | | Message-Id: <200805101252.11961.chromatic@wgz.org> p4raw-id: //depot/perl@33858
* New separations for the pattern match operator documentation,David Nicol2008-05-181-0/+6
| | | | | | | | | suggested by David Nicol: Subject: It's wafer thin! From: "David Nicol" <davidnicol@gmail.com> Message-ID: <934f64a20805091114y40595f9ap9d355b39f20779c1@mail.gmail.com> p4raw-id: //depot/perl@33852
* Modulo operator and floating point numbersKen Williams2008-02-181-5/+7
| | | | | | From: "Ken Williams" <kenahoo@gmail.com> Message-ID: <6a7ee8cc0802162122r4e59b93boee18b1f045b8954d@mail.gmail.com> p4raw-id: //depot/perl@33328
View Lorry Controller Status