Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Gerd Stolpmann <Gerd.Stolpmann@darmstadt.netsurf.de>
To: caml-list@inria.fr
Subject: New software: xstr - Thread-safe string functions
Date: Wed, 7 Jul 1999 22:15:12 +0200	[thread overview]
Message-ID: <99070722283603.28040@schneemann> (raw)

>From the README:

	This package implements frequent string operations: searching, replacing,
	splitting, matching. It is independent from the Str library, and can 
	replace Str in many cases. Unlike Str, xstr is thread-safe. xstr does
	not implement regular expressions in general, but an important subset.
	Some operations of xstr are performed as quickly as by Str; if the string
	to be processed is small, xstr is often faster than Str; if the string is
	big, xstr is upto half as fast as Str. 

You can download the package from the usual place:

	http://people.darmstadt.netsurf.de/Gerd.Stolpmann/ocaml/

This package has an entry in the O'Caml link database; updates are announced
here:

	http://www.npc.de/ocaml/linkdb/

Note: that xstr is often slower than Str (which bases on the GNU regex library)
is partly caused by the missing bitstrings. As substitute I use an array of
16 integers storing 16 bits each. The membership-test for bitstrings is the
most frequent operation, and it must be fast to get good results. What I would
need is a primitive that finds the next character in a string that is member of
a given bitstring. Most time-consuming loops in xstr do exactly this.


Gerd
--
----------------------------------------------------------------------------
Gerd Stolpmann      Telefon: +49 6151 997705 (privat)
Viktoriastr. 100             
64293 Darmstadt     EMail:   Gerd.Stolpmann@darmstadt.netsurf.de (privat)
Germany                     
----------------------------------------------------------------------------



                 reply	other threads:[~1999-07-08  2:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=99070722283603.28040@schneemann \
    --to=gerd.stolpmann@darmstadt.netsurf.de \
    --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