From: Jerome Vouillon <vouillon@pps.jussieu.fr>
To: John Skaller <skaller@ozemail.com.au>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Regarding regular expressions
Date: Wed, 7 Aug 2002 09:36:00 +0200 [thread overview]
Message-ID: <20020807073600.GA31615@strontium.pps.jussieu.fr> (raw)
In-Reply-To: <3D50A9E8.9060605@ozemail.com.au>
> For a language where backreferences are available, I thought it would be
> interesting to see how often people make use of this feature. So I
> downloaded the CPAN archive and analyzed the perl scripts there. Here
> is what I found:
>
> - I found 165228 perl scripts/modules in CPAN [1].
> - Of those, 68501 use regular expressions [2].
> - Of those, 32359 (or 47 percent) use backreferences [3].
>
> So, nearly half of all perl scripts on CPAN that use regular expressions
> make use of the backreference feature. IMO this argues strongly in
> favor of supporting backreferences in C++. (Backreferences can only be
> handled by a backtracking NFA engine, IIRC.)
What he means by backreference is a way to refer to a submatch. For
instance, with the regular expression "^([^ ]*) *([^ ]*)", the
backreference "$1" will refer to the substring matched by the first
parenthesed subexpression "([^ ]*)". As long as the references do not
occur in the regular expression itself, they can be handled perfectly
well with a DFA engine. So, the numbers above do not prove anything.
> There are other features besides backreferences that can only be
> provided by a backtracking NFA. These features include non-greedy
> quantification, positive and negative look-ahead and look-behind
> assertions, independent sub-expressions, conditional sub-expressions,
> and backreferences within the pattern itself.
I believe all these features but backreferences within a pattern can
be provided by a DFA engine (though my RE library only support one of
these features, non-greedy quantification, at the moment).
So, the real questions are:
- how often are backreferences used within a pattern?
- when they are used, is it just for convenience, or would it be hard
to rewrite the pattern without using backreferences?
[Feel free to forward this mail back to the C++ commitee.]
-- Jerome
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-08-07 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 5:02 John Skaller
2002-08-07 7:36 ` Jerome Vouillon [this message]
2002-08-07 12:23 ` Pixel
2002-08-07 14:41 ` [Caml-list] Three way comparaisons Diego Olivier Fernandez Pons
2002-08-07 15:22 ` Luc Maranget
2002-08-08 11:44 ` Diego Olivier Fernandez Pons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020807073600.GA31615@strontium.pps.jussieu.fr \
--to=vouillon@pps.jussieu.fr \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox