From: Markus Mottl <markus.mottl@gmail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Immutable strings
Date: Fri, 4 Jul 2014 17:01:18 -0400 [thread overview]
Message-ID: <CAP_800rUwwmYYs7fSKt-i2SnFxPGLo+9fczijR=U0Z7GaQhicA@mail.gmail.com> (raw)
In-Reply-To: <1404501528.4384.4.camel@e130>
I agree that the new concept has some noteworthy downsides as
demonstrated in the Lexing-example. Your proposed solution 2
(stringlike) would probably solve these issues from a safety point of
view. The downside is that the complexity of string-handling would
increase even more, because then we would have three types to deal
with. I personally prefer safety over convenience, but other people's
(especially beginner's) mileage may vary.
The Bigarray-approach doesn't seem appealing to me. Strings are much
more lightweight, since they can be allocated cheaply on the
OCaml-heap. E.g. String.create is about 10x-100x faster than
Bigarray.create. That seems too big to ignore.
Regards,
Markus
On Fri, Jul 4, 2014 at 3:18 PM, Gerd Stolpmann <info@gerd-stolpmann.de> wrote:
> Hi list,
>
> I've just posted a blog article where I criticize the new concept of
> immutable strings that will be available in OCaml 4.02 (as option):
>
> http://blog.camlcity.org/blog/bytes1.html
>
> In short my point is that it the new concept is not far reaching enough,
> and will even have negative impact on the code quality when it is not
> improved. I also present three ideas how to improve it.
>
> Gerd
> --
> ------------------------------------------------------------
> Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
> My OCaml site: http://www.camlcity.org
> Contact details: http://www.camlcity.org/contact.html
> Company homepage: http://www.gerd-stolpmann.de
> ------------------------------------------------------------
>
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
--
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
next prev parent reply other threads:[~2014-07-04 21:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 19:18 Gerd Stolpmann
2014-07-04 20:31 ` Anthony Tavener
2014-07-04 20:38 ` Malcolm Matalka
2014-07-04 23:44 ` Daniel Bünzli
2014-07-05 11:04 ` Gerd Stolpmann
2014-07-16 11:38 ` Damien Doligez
2014-07-04 21:01 ` Markus Mottl [this message]
2014-07-05 11:24 ` Gerd Stolpmann
2014-07-08 13:23 ` Jacques Garrigue
2014-07-08 13:37 ` Alain Frisch
2014-07-08 14:04 ` Jacques Garrigue
2014-07-28 11:14 ` Goswin von Brederlow
2014-07-28 15:51 ` Markus Mottl
2014-07-29 2:54 ` Yaron Minsky
2014-07-29 9:46 ` Goswin von Brederlow
2014-07-29 11:48 ` John F. Carr
2014-07-07 12:42 ` Alain Frisch
2014-07-08 12:24 ` Gerd Stolpmann
2014-07-09 13:54 ` Alain Frisch
2014-07-09 18:04 ` Gerd Stolpmann
2014-07-10 6:41 ` Nicolas Boulay
2014-07-14 17:40 ` Richard W.M. Jones
2014-07-08 18:15 ` mattiasw
2014-07-08 19:24 ` Daniel Bünzli
2014-07-08 19:27 ` Raoul Duke
2014-07-09 14:15 ` Daniel Bünzli
2014-07-14 17:45 ` Richard W.M. Jones
2014-07-21 15:06 ` Alain Frisch
[not found] ` <20140722.235104.405798419265248505.Christophe.Troestler@umons.ac.be>
2014-08-29 16:30 ` Damien Doligez
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='CAP_800rUwwmYYs7fSKt-i2SnFxPGLo+9fczijR=U0Z7GaQhicA@mail.gmail.com' \
--to=markus.mottl@gmail.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
/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