From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pBN0jU1n013224
	for <caml-list@sympa-roc.inria.fr>; Fri, 23 Dec 2011 01:45:32 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvABAK/O807AbSoIe2dsb2JhbABDhQ+kTIJXIgEBFiYEIYFyAQEEASMPAUYFCwsJDwICJgICFBgxiA0CpVqRUROBHIlKM2MEjUaHOpI0
X-IronPort-AV: E=Sophos;i="4.71,396,1320620400"; 
   d="scan'208";a="136534256"
Received: from einhorn.in-berlin.de ([192.109.42.8])
  by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Dec 2011 01:45:32 +0100
X-Envelope-From: oliver@first.in-berlin.de
Received: from first (e178031165.adsl.alicedsl.de [85.178.31.165])
	(authenticated bits=0)
	by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id pBN0jVSm027829
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 23 Dec 2011 01:45:31 +0100
Received: by first (Postfix, from userid 1000)
	id 8591E1540357; Fri, 23 Dec 2011 01:45:30 +0100 (CET)
Date: Fri, 23 Dec 2011 01:45:30 +0100
From: oliver <oliver@first.in-berlin.de>
To: =?utf-8?B?U3TDqXBoYW5l?= Glondu <steph@glondu.net>
Cc: caml-list@inria.fr
Message-ID: <20111223004530.GB12304@siouxsie>
References: <20111222183914.GA6185@siouxsie>
 <4EF38AD4.10608@glondu.net>
 <20111222213956.GA8513@siouxsie>
 <4EF3B0BD.7040900@glondu.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4EF3B0BD.7040900@glondu.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8
Subject: Re: [Caml-list] Fatal error: exception Pcre.Error(0)

On Thu, Dec 22, 2011 at 11:35:41PM +0100, Stéphane Glondu wrote:
> Le 22/12/2011 22:39, oliver a écrit :
> >>> where is there a documentation about these kind of errors from pcre-lib?
> >>> I'm using Pcre.pmatch, which should just give me a bool.
> >>
> >> See pcre.mli. Pcre.Error(0) is the raw representation of Partial (i.e.
> >> string only matched the pattern partially).
> > [...]
> > 
> > In my pcre.mli this error is not mentioned.
> > 
> > There is a
> > 
> > 
> > type error =
> >   | Partial  (** String only matched the pattern partially *)
>       ^^^^^^^
> 
> There.
> 
> > Which also mentioned a partial-match error.
> > But Pcre.Error(0) looks somehow cryptical
> > and strange to me.
> 
> Pcre.Error(0) is cryptical but not strange: it is the same as
> Pcre.Error(Pcre.Partial).
[...]


> Whatever gives you the error message

... would be interesting to know.

In some other code with partial matches, I got no error...
(with or without the partial-flag).

And I also would not await an error at all...

The difference between the true/false result and the
Pcre.Error(0) result is, that the latter one occurs in
recursive calls of a function.

But AFAIK pcre-ocaml should have no problem here...
...and it's not even multithreaded, but even there,
nothing like that should happen...?!


> mentioning Pcre.Error(0) does not have access to type information, so it
> cannot give you more than Pcre.Error(0). You didn't tell where the error
> message came from.

Can you be more precise in what you mean with where it comes from?
If the exception is called Pcre.Error(0) I would assume it., coming from
Pcre module.


Ciao,
   Oliver