From: Alex Baretta <alex@barettadeit.com>
To: Christophe TROESTLER <Christophe.Troestler@umh.ac.be>,
Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Thread safe Str
Date: Mon, 10 Jan 2005 10:57:28 +0100 [thread overview]
Message-ID: <41E25188.3030004@barettadeit.com> (raw)
In-Reply-To: <20050109.203010.110660321.Christophe.Troestler@umh.ac.be>
Christophe TROESTLER wrote:
> Hi,
>
> The new Str module not only made it LGPL but also very fast (100% more
> than Pcre in some cases). However it is still not thread safe -- and
> it is not possible given its interface. However, from a quick look,
> it seems to me that what is under the hood is almost thread safe. So
> why not to write a new module (say Regexp) which would be thread safe
> and on top of which Str would be build? This would not be too much
> work, would it?
>
> Cheers,
> ChriS
I think I remember a thread where Xavier explained that Str is fully
thread safe because all state data structures are allocated on a
per-thread basis.
Alex
--
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL
tel. +39 02 370 111 55
fax. +39 02 370 111 54
Our technology:
The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/>
The FreerP Project
<http://www.freerp.org/>
next prev parent reply other threads:[~2005-01-10 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:30 Christophe TROESTLER
2005-01-09 20:57 ` [Caml-list] " Gerd Stolpmann
2005-01-10 9:57 ` Alex Baretta [this message]
2005-01-10 15:49 ` Xavier Leroy
2005-01-10 16:39 ` Richard Jones
2005-01-10 18:21 ` Eric C. Cooper
2005-01-10 20:25 ` Martin Jambon
2005-01-11 3:54 ` skaller
2005-01-11 7:03 ` Chris King
2005-01-11 8:06 ` skaller
2005-01-11 12:08 ` Gerd Stolpmann
2005-01-11 17:55 ` skaller
2005-01-11 20:30 ` Gerd Stolpmann
2005-01-12 7:42 ` skaller
[not found] ` <875c7e070501111007dc3e86d@mail.gmail.com>
[not found] ` <1105471138.2574.88.camel@pelican.wigram>
[not found] ` <875c7e07050111115618692184@mail.gmail.com>
2005-01-11 19:58 ` Chris King
2005-01-11 20:53 ` Martin Jambon
2005-01-12 7:59 ` skaller
2005-01-12 20:12 ` Martin Jambon
2005-01-11 6:41 ` Chris King
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=41E25188.3030004@barettadeit.com \
--to=alex@barettadeit.com \
--cc=Christophe.Troestler@umh.ac.be \
--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).