summaryrefslogtreecommitdiff
path: root/pod/perlfaq4.pod
diff options
context:
space:
mode:
authorAbigail <abigail@abigail.be>2002-07-30 02:52:02 -0700
committerhv <hv@crypt.org>2002-08-12 11:17:21 +0000
commitf0f835c2976ada1bb00d5ec52c67c4546ac5d689 (patch)
treec8a9ba9da41469c4c28534743ea979e5752ae247 /pod/perlfaq4.pod
parent969db73bd1eabde66aa428082d72b0d7d5f6ce78 (diff)
downloadperl-f0f835c2976ada1bb00d5ec52c67c4546ac5d689.tar.gz
pod/perlfaq4.pod
Message-id: <20020730095202.A6462@ucan.foad.org> Add references to Regexp::Common. p4raw-id: //depot/perl@17710
Diffstat (limited to 'pod/perlfaq4.pod')
-rw-r--r--pod/perlfaq4.pod9
1 files changed, 6 insertions, 3 deletions
diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod
index 18d709169b..f2512059cc 100644
--- a/pod/perlfaq4.pod
+++ b/pod/perlfaq4.pod
@@ -575,8 +575,9 @@ matter how complicated. To find something between two single
characters, a pattern like C</x([^x]*)x/> will get the intervening
bits in $1. For multiple ones, then something more like
C</alpha(.*?)omega/> would be needed. But none of these deals with
-nested patterns, nor can they. For that you'll have to write a
-parser.
+nested patterns. For balanced expressions using C<(>, C<{>, C<[>
+or C<< < >> as delimiters, use the CPAN module Regexp::Common, or see
+L<perlre/(??{ code })>. For other cases, you'll have to write a parser.
If you are serious about writing a parser, there are a number of
modules or oddities that will make your life a lot easier. There are
@@ -1926,7 +1927,9 @@ Assuming that you don't care about IEEE notations like "NaN" or
You can also use the L<Data::Types|Data::Types> module on
the CPAN, which exports functions that validate data types
-using these and other regular expressions.
+using these and other regular expressions, or you can use
+the C<Regexp::Common> module from CPAN which has regular
+expressions to match various types of numbers.
If you're on a POSIX system, Perl's supports the C<POSIX::strtod>
function. Its semantics are somewhat cumbersome, so here's a C<getnum>