From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ANNOUNCE: mod_caml 1.0.6 - includes security patch
Date: Fri, 16 Jan 2004 09:34:54 +0000 [thread overview]
Message-ID: <20040116093454.GA23909@redhat.com> (raw)
In-Reply-To: <6290BE91-47EB-11D8-A8F5-000393B8133A@wetware.com>
On Thu, Jan 15, 2004 at 10:15:30PM -0800, james woodyatt wrote:
> On 15 Jan 2004, at 08:53, Richard Jones wrote:
> >On Thu, Jan 15, 2004 at 05:19:44PM +0100, Markus Mottl wrote:
> >>I know it looks awful, but the four backslashes in the regexp
> >>pattern for re2 indeed only stand for one. They have to be escaped
> >>in the OCaml-string and also for PCRE again,
> >>i.e. twice. Substitution patterns use the $-sign for escaping -
> >>therefore escaping only needs to be done once.
> >
> >Another reason to hasten the addition of regular expressions to the
> >OCaml lexer, 'a la Perl!
>
> Doesn't the lexer already have regular expressions? I think you mean
> something to make regular expressions into first-class values in the
> language. I'm not sure that's necessary.
Being able to write:
var ~ /ab+/
and similar certainly makes string handling and simple parsing a lot
easier.
Rich.
--
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
Perl4Caml lets you use any Perl library in your type-safe Objective
CAML programs. http://www.merjis.com/developers/perl4caml/
-------------------
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:[~2004-01-16 9:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 14:03 Richard Jones
[not found] ` <4006AC01.F2AD2741@decis.be>
2004-01-15 15:42 ` Richard Jones
2004-01-15 16:19 ` Markus Mottl
2004-01-15 16:53 ` Richard Jones
2004-01-16 6:15 ` james woodyatt
2004-01-16 9:34 ` Richard Jones [this message]
2004-01-16 19:05 ` Brian Hurt
2004-01-16 18:52 ` Yutaka OIWA
2004-01-16 19:20 ` Markus Mottl
2004-01-16 19:01 ` Markus Mottl
2004-01-19 10:13 ` Luc Maranget
2004-01-19 11:36 ` Richard Jones
2004-01-19 14:43 ` Luc Maranget
2004-01-19 16:10 ` Richard Jones
2004-01-19 17:46 ` Markus Mottl
2004-01-19 18:05 ` Richard Jones
2004-01-19 21:45 ` Eray Ozkural
2004-01-20 11:31 ` Markus Mottl
2004-01-20 12:30 ` Eray Ozkural
2004-01-21 14:01 ` skaller
2004-01-20 17:34 ` Michal Moskal
2004-01-20 17:52 ` Eray Ozkural
2004-01-20 18:54 ` Michal Moskal
2004-01-20 19:21 ` Markus Mottl
2004-01-20 19:37 ` David Brown
2004-01-20 20:38 ` Eray Ozkural
2004-01-21 19:07 ` Max Kirillov
[not found] ` <Pine.GSO.4.53.0401211150520.10508@cascade.cs.ubc.ca>
2004-01-22 2:15 ` Max Kirillov
2004-01-20 23:00 ` Brian Hurt
2004-01-20 23:48 ` Eray Ozkural
2004-01-21 0:34 ` David Brown
2004-01-21 2:32 ` Eray Ozkural
2004-01-21 2:34 ` Eray Ozkural
2004-01-21 2:34 ` Shawn Wagner
2004-01-21 9:43 ` Andreas Rossberg
2004-01-21 5:16 ` Brian Hurt
2004-01-19 21:59 ` Kenneth Knowles
2004-01-19 18:18 ` David Brown
2004-01-19 19:15 ` Markus Mottl
2004-01-19 19:19 ` David Brown
[not found] ` <20040119185746.A12690@beaune.inria.fr>
2004-01-19 18:07 ` Richard Jones
2004-01-20 1:29 ` skaller
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=20040116093454.GA23909@redhat.com \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).