From: Jean-Christophe Filliatre <Jean-Christophe.Filliatre@lri.fr>
To: "Agustín Valverde" <a_valverde@ctima.uma.es>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Better option to read a file
Date: Wed, 17 Mar 2004 09:22:19 +0100 [thread overview]
Message-ID: <16472.2747.9259.155336@gargle.gargle.HOWL> (raw)
In-Reply-To: <E2DFEE92-7790-11D8-938F-000393B21E00@ctima.uma.es>
Agustín Valverde writes:
> Second:
>
> let rec unir c ac = unir ac^(Char.escaped c);;
>
> let leer2 fl =
> let form = ref "" in
> let c = ref '-' in
> let arch = open_in fl in
> (try
> (while true do (c := input_char arch); (if !c != '\n' then (form
> := unir !c !form) else ()) done)
> with End_of_file -> close_in arch);
> !form;;
Note that this function is very inefficient: you are indeed building a
lot of intermediate strings with "unir", resulting in a quadratic
space (even if the final string occupies linear space).
Using a buffer as suggested by Christoph is clearly better (the module
Buffer from ocaml standard library is doubling its internal string
buffer as needed, without you to worry about it).
> I also have a parser to convert the string, could I to improve these
> functions merging them with the parser in some way?
The use of ocamllex in combination with a buffer is both easy and
efficient. I sketch it:
======================================================================
{
open Lexing
let buf = Buffer.create 1024
}
rule read = parse
| "\\n" { Buffer.add_char buf '\n'; read lexbuf }
| "\\t" { Buffer.add_char buf '\t'; read lexbuf }
| "\\\\" { Buffer.add_char buf '\\'; read lexbuf }
| _ { Buffer.add_string buf (lexeme lexbuf); read lexbuf }
| eof { Buffer.contents buf }
{
let read_file f =
let cin = open_in f in
let lb = from_channel cin in
let s = read lb in
close_in cin;
s
}
======================================================================
--
Jean-Christophe Filliâtre (http://www.lri.fr/~filliatr)
-------------------
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-03-17 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 21:28 Agustín Valverde
2004-03-17 3:48 ` Pietro Abate
2004-03-17 7:31 ` Christoph Bauer
2004-03-17 16:42 ` Agustin Valverde Ramos
2004-03-17 17:46 ` Markus Mottl
2004-03-17 18:20 ` Agustin Valverde Ramos
2004-03-17 18:54 ` Markus Mottl
2004-03-17 8:22 ` Jean-Christophe Filliatre [this message]
2004-03-17 10:11 ` Markus Mottl
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 20:38 Agustín Valverde
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=16472.2747.9259.155336@gargle.gargle.HOWL \
--to=jean-christophe.filliatre@lri.fr \
--cc=a_valverde@ctima.uma.es \
--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