From: Markus Mottl <markus@oefai.at>
To: skaller <skaller@users.sourceforge.net>
Cc: Richard Jones <rich@annexia.org>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] unix.chop_extension
Date: Thu, 27 May 2004 09:46:34 +0200 [thread overview]
Message-ID: <20040527074634.GA27994@fichte.ai.univie.ac.at> (raw)
In-Reply-To: <1085633313.32106.110.camel@pelican.wigram>
On Thu, 27 May 2004, skaller wrote:
> AFAIK: The C Pcre that it wraps does use global variables
> and so while the interface appears re-entrant
> it isn't.
To prevent people from getting a false impression of PCRE as interfaced
to OCaml: it _is_ safe. Calling PCRE-functions from threads or executing
two different regular expressions in an intermittent way should never
crash your program or lead to unexpected results.
The use of global variables by the C-library does not necessarily imply
that the program is unsafe. It all depends on their use, and in this
case the global variables (e.g. pcre_callout) are initialized exactly
once at startup time, i.e. before the user can access any functions.
Libraries implemented in imperative style may still have reentrant
interfaces.
--
Markus Mottl http://www.oefai.at/~markus markus@oefai.at
-------------------
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-05-27 7:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 20:04 skaller
2004-05-24 22:01 ` skaller
2004-05-25 8:46 ` Alex Baretta
2004-05-25 9:35 ` skaller
2004-05-25 9:46 ` Alain Frisch
2004-05-25 10:47 ` skaller
2004-05-25 11:51 ` sejourne kevin
2004-05-26 11:18 ` Florian Hars
2004-05-25 14:06 ` [Caml-list] Re: AAP (was: unix.chop_extension) Christophe TROESTLER
2004-05-25 13:37 ` [Caml-list] unix.chop_extension John Goerzen
2004-05-25 19:17 ` Richard Jones
2004-05-27 8:15 ` YANG Shouxun
2004-05-27 9:47 ` skaller
2004-05-26 9:05 ` Xavier Leroy
2004-05-26 9:35 ` Luca Pascali
2004-05-26 9:56 ` Remi Vanicat
2004-05-26 10:34 ` skaller
2004-05-26 13:27 ` Damien Doligez
2004-05-26 15:50 ` skaller
2004-05-26 16:04 ` Damien Doligez
2004-05-27 4:33 ` skaller
2004-05-27 4:56 ` John Goerzen
2004-05-28 16:44 ` Damien Doligez
2004-05-28 19:34 ` skaller
2004-05-29 8:37 ` Damien Doligez
2004-05-29 10:01 ` skaller
2004-05-29 16:02 ` David Brown
2004-05-26 11:21 ` Alex Baretta
2004-05-26 16:43 ` Richard Jones
2004-05-27 4:48 ` skaller
2004-05-27 7:46 ` Markus Mottl [this message]
2004-05-27 9:33 ` skaller
2004-05-27 17:29 ` brogoff
2004-05-28 12:00 ` Keith Wansbrough
2004-05-28 16:43 ` brogoff
2004-05-28 17:49 ` Marcin 'Qrczak' Kowalczyk
2004-05-28 11:23 ` Alex Baretta
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=20040527074634.GA27994@fichte.ai.univie.ac.at \
--to=markus@oefai.at \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
--cc=skaller@users.sourceforge.net \
/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