From: "Eric C. Cooper" <ecc@cmu.edu>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Strings as arrays or lists...
Date: Mon, 3 Mar 2003 21:49:20 -0500 [thread overview]
Message-ID: <20030304024920.GA24512@stratocaster.home> (raw)
In-Reply-To: <20030302193437.A6487@pauillac.inria.fr>
On Sun, Mar 02, 2003 at 07:34:37PM +0100, Xavier Leroy wrote:
> Actually, the list representation of strings is so repugnant that I
> don't even want to include "explode" and "implode" coercions between
> string and char list in the standard library. A standard library
> should steer users away from algorithmically-inefficient code. By not
> having implode and explode in the library, I hope OCaml programmers
> will come to the realization that the proper way to operate on strings
> is either via block operations (the String module, regexps, etc), or
> by recursion on integer indices.
I recently wrote some code that made use of char lists, and explode
and implode came in handy. I needed to marshal a recursive datatype
into a packet to be sent over a communication channel according to a
protocol that imposed a specific format, including a length byte at
the beginning and a checksum byte at the end.
I could have made one pass over the data to compute the packet length,
then a second pass marshaling it into a buffer. But it was very
natural to just build up a list of bytes in a single traversal of the
datatype. Then the length and checksum could easily be added to the
beginning and the end, and the result written out.
I used explode when I encountered string values at the leaves of the
datatype. I didn't really need implode (I could just iterate
output_byte over the final list), but it came in handy for dumping
packets for debugging.
I wasn't really using char lists as a representation of strings, but
rather as a buffer-like data structure that just happened to need
conversion to and from strings at certain points.
As another poster pointed out, explode and implode are analogous to
Array.to_list and Array.of_list, which don't seem to entice OCaml
programmers down the path of algorithmic ineffiency.
--
Eric C. Cooper e c c @ c m u . e d u
-------------------
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:[~2003-03-04 2:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:31 Oliver Bandel
2003-02-28 1:03 ` brogoff
2003-03-02 18:34 ` Xavier Leroy
2003-03-02 19:03 ` Alain.Frisch
2003-03-03 8:50 ` Luc Maranget
2003-03-03 17:12 ` brogoff
2003-03-03 17:40 ` Diego Olivier Fernandez Pons
2003-03-04 2:49 ` Eric C. Cooper [this message]
2003-03-04 8:29 ` Fabrice Le Fessant
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=20030304024920.GA24512@stratocaster.home \
--to=ecc@cmu.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