Return-Path: <balld@webslingerZ.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 44600 invoked from network); 12 May 2000 18:21:15 -0000
Received: from balld-0.dsl.speakeasy.net (HELO localhost.localdomain)
 (@216.254.77.75)
  by locus.apache.org with SMTP; 12 May 2000 18:21:15 -0000
Received: from localhost (balld@localhost)
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id OAA09413
	for <cocoon-dev@xml.apache.org>; Fri, 12 May 2000 14:20:56 -0400
X-Authentication-Warning: localhost.localdomain: balld owned process doing -bs
Date: Fri, 12 May 2000 14:20:55 -0400 (EDT)
From: Donald Ball <balld@webslingerZ.com>
X-Sender: balld@localhost.localdomain
To: cocoon-dev@xml.apache.org
Subject: Re: [Cocoon 2] Regex matchers :-)
In-Reply-To: <391C0322.9F4699A0@apache.org>
Message-ID: <Pine.LNX.4.10.10005121418330.7014-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Fri, 12 May 2000, Stefano Mazzocchi wrote:

> Now, how can this work using full regexp? say we allow the use of
> pluggable matching with sort of XPointer syntax
> 
>  <redirect 
>   source="regexp(/htdocs/foo/[a|b|c]/index.html)" 
>   target="/xdocs/*/index"
>  />
> 
> What does the star mean? [a|b|c]? I can't see how this can be easier
> than using wildcards... less verbose, totally, but reducing verbosity
> doesn't always increase readability, expecially in configurations.

you would do this:

<redirect
 source="regexp(/htdocs/foo/([a|b|c])/index.html)"
 target="/xdocs/$1/index"
/>

$1 refers to the first paranthesized match, $2 the second, etc. Have you
never used perl or general UNIX regexps before? The pattern matching and
variable referral rules are well understood.

- donald