Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Tue, 20 Jun 2006 17:25:12 +0100
From: Joe Orton <jorton@redhat.com>
To: dev@httpd.apache.org
Subject: Re: Trouble with the bundled PCRE
Message-ID: <20060620162512.GA10361@redhat.com>
Mail-Followup-To: dev@httpd.apache.org
References: <1f9222b70606200339p2ca101eci24a06ce0d67b158c@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <1f9222b70606200339p2ca101eci24a06ce0d67b158c@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i

On Tue, Jun 20, 2006 at 11:39:29AM +0100, Ivan Ristic wrote:
> I have a problem with the bundled PCRE that I am not sure how to
> resolve. Basically, in a module I need to access more functionality
> than provided by the Apache PCRE wrapper. (More specifically, I need
> to perform matching against strings that are not NULL-terminated.) I
> can do this if I have the Apache source code around, simply by using
> the PCRE headers that are in the source tree. But I can't do that when
> there is no source code since the PCRE headers are not available. Is
> there a smart way around this? Am I missing anything?
> 
> Is there a reason for not including the PCRE headers in the /include/
> directory of the Apache installation?

It doesn't make sense to do that since httpd might be configured using 
an external copy of PCRE (configure --with-pcre).  Exposing more of PCRE 
through ap_regex.h might be OK, it depends on what exactly you propose.

Regards,

joe