From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: Gerd Stolpmann <gerd@gerd-stolpmann.de>
Cc: Miles Egan <miles@caddr.com>, OCAML <caml-list@inria.fr>
Subject: Re: features of PCRE-OCaml
Date: Fri, 8 Dec 2000 16:05:07 +0100 [thread overview]
Message-ID: <20001208160507.A22011@miss.wu-wien.ac.at> (raw)
In-Reply-To: <00120813571607.00625@ice>; from gerd@gerd-stolpmann.de on Fri, Dec 08, 2000 at 13:30:55 +0100
Gerd Stolpmann schrieb am Friday, den 08. December 2000:
> However, the PCRE stubs can be improved in one point: The master lock could be
> released while the engine executes the regexp. Several threads could then
> use the engine at the same time which would improve the responsiveness of
> multi-threaded programs, and the programs would run faster on SMP systems.
Are there annotations which one could use to indicate reentrancy of
external functions? This would make it fairly easy to get rid of this
problem. This information could then also be used for program analysis.
- Markus Mottl
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next prev parent reply other threads:[~2000-12-11 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 0:51 Markus Mottl
2000-12-07 16:01 ` John Max Skaller
2000-12-07 16:32 ` Markus Mottl
2000-12-07 17:08 ` John Max Skaller
2000-12-08 0:03 ` Markus Mottl
2000-12-08 17:52 ` John Max Skaller
2000-12-08 9:19 ` Alain Frisch
2000-12-08 18:11 ` John Max Skaller
2000-12-08 19:48 ` Alain Frisch
2000-12-09 17:07 ` John Max Skaller
2000-12-14 17:35 ` unicode support Nickolay Semyonov
2000-12-07 20:17 ` features of PCRE-OCaml Miles Egan
2000-12-08 12:30 ` Gerd Stolpmann
2000-12-08 15:05 ` Markus Mottl [this message]
2000-12-08 15:40 ` Gerd Stolpmann
2000-12-09 3:03 ` Markus Mottl
2000-12-09 13:12 ` Gerd Stolpmann
2000-12-10 0:32 ` Markus Mottl
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=20001208160507.A22011@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--cc=caml-list@inria.fr \
--cc=gerd@gerd-stolpmann.de \
--cc=miles@caddr.com \
/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).