caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yitzhak Mandelbaum <yitzhakm@CS.Princeton.EDU>
To: Caml-list List <caml-list@inria.fr>
Subject: buffered io library
Date: Thu, 12 Mar 2009 21:02:39 -0400	[thread overview]
Message-ID: <0E8C587F-F0BF-4B4D-A4A5-88ADB632D3F5@cs.princeton.edu> (raw)

Hi,

I'm looking for an efficient IO library geared towards support for  
things like lexers. The essential features are:
* Support for easily backing up in the IO stream. That is, it should  
have an API for saving one's place and then later discarding that save  
(i.e. committing to current position) or restoring the IO stream to  
the saved location.
* Support for extracting and/or accessing sections of the stream  
(particularly, those between the last save point and the current  
position).

It looks like the Lexing module has these features baked in, but it  
doesn't seem to expose them to the user.  Does anyone have any other  
suggestions?

Thanks,
Yitzhak
-----------------------------
Yitzhak Mandelbaum




                 reply	other threads:[~2009-03-13  1:02 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=0E8C587F-F0BF-4B4D-A4A5-88ADB632D3F5@cs.princeton.edu \
    --to=yitzhakm@cs.princeton.edu \
    --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).