From: skaller <skaller@users.sourceforge.net>
To: Jon Harrop <jon@jdh30.plus.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] String to list to string
Date: 11 Feb 2005 12:22:02 +1100 [thread overview]
Message-ID: <1108084921.16698.213.camel@pelican.wigram> (raw)
In-Reply-To: <200502101928.26511.jon@jdh30.plus.com>
On Fri, 2005-02-11 at 06:28, Jon Harrop wrote:
> On Thursday 10 February 2005 18:35, Harrison, John R wrote:
> > ...I consider OCaml's mutable strings a far worse design error.
>
> That's interesting. Why?
Because it makes the worst possible compromise.
Throws out transparency/persistence and fails to
allow any length changing operations, which are
common for strings -- overwriting strings is rarely
needed. The only use I can think of is as a buffer
(and we have Buffer module for that, and it
also allows variable length)
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
next prev parent reply other threads:[~2005-02-11 1:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 18:35 Harrison, John R
2005-02-10 19:28 ` Jon Harrop
2005-02-11 1:22 ` skaller [this message]
2005-02-11 2:05 ` John Prevost
2005-02-10 19:32 ` brogoff
-- strict thread matches above, loose matches on Subject: below --
2005-02-10 21:18 Harrison, John R
2005-02-10 19:51 Harrison, John R
2005-02-07 2:24 Fwd: Re: [Caml-list] The boon of static type checking Jon Harrop
2005-02-10 2:10 ` String to list to string Juancarlo Añez
2005-02-10 2:27 ` [Caml-list] " William D.Neumann
2005-02-10 3:24 ` Erik de Castro Lopo
2005-02-10 6:31 ` Radu Grigore
2005-02-10 6:52 ` Erik de Castro Lopo
2005-02-10 3:41 ` Jon Harrop
2005-02-15 1:16 ` Aaron Bohannon
2005-02-15 10:33 ` Richard Jones
2005-02-15 13:34 ` Eric C. Cooper
2005-02-10 10:09 ` Richard Jones
2005-02-10 19:19 ` Juancarlo Añez
[not found] ` <E1CzJqb-00031c-00@furbychan.cocan.org>
2005-02-10 19:41 ` Richard Jones
2005-02-10 17:58 ` brogoff
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=1108084921.16698.213.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=jon@jdh30.plus.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).