From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ask for a more efficient way to deallocate memory (full version)
Date: Sat, 15 Dec 2007 22:33:34 +0100 [thread overview]
Message-ID: <1197754414.4764482e09e3f@webmail.in-berlin.de> (raw)
In-Reply-To: <200712102259.30602.jon@ffconsultancy.com>
Zitat von Jon Harrop <jon@ffconsultancy.com>:
> On Monday 10 December 2007 22:13, Oliver Bandel wrote:
> > Because I don't know how it's implemented, I don't know if this
> adds a
> > performance lack. But possibly it would make sense to look at it
> closer
> > to explore it's advantages and disadvantages...
> > ...but I've no experience in OCaml extension, so I hope someone
> here can
> > say some wprds about it.
>
> OCaml has a great macro system called camlp4 that lets you add new
> syntactic
> constructs and rewrite OCaml code at will.
Yes, so far I know it.
> So Martin's code adds a
> new
> syntactic construct and automatically injects the code for the
> compiler that
> we must currently write by hand. Consequently, its performance will
> be
> superb: as good as hand-written OCaml code.
So, is it just a kind of pre-compilation?
The core-OCaml compiler will be the same?
Is the TryFinally-code slight enough, so that
it's behaving like handwritten OCaml? Did you look
at the TryFinally in detail?
>
> However, using any camlp4 macros requires using the camlp4
> replacement for the
> front-end of the compiler.
I have not looked at the OCaml-compiler in detail,
but from what you wrote I would assume, there
are at least two parts.
> That uses a different parsing technology
> (top-down
> recursive descent LL rather than bottom-up LALR) so the error
> messages from
> the compiler are completely different.
Oh, well.... that's new to me.
I had not needed camlp4 so far. And I don't know if it makes sense to
look at it now, because there will be (or already is?) a replacement
(from 3.10 on?).
I hope the camlp4-tutorial will be updated to the camlp4-replacement.
Possibly later I might use it. Then it would be good to have
introductional material.
Ciao,
Oliver
next prev parent reply other threads:[~2007-12-15 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 21:39 Fabrice.Pardo
2007-12-09 21:55 ` [Caml-list] " Olivier Andrieu
2007-12-10 11:25 ` Fabrice Pardo
2007-12-10 12:03 ` Michaël Le Barbier
2007-12-10 16:33 ` Oliver Bandel
2007-12-10 20:27 ` Richard Jones
2007-12-10 21:05 ` Oliver Bandel
2007-12-10 21:15 ` Gordon Henriksen
2007-12-10 22:13 ` Oliver Bandel
2007-12-10 22:59 ` Jon Harrop
2007-12-10 23:29 ` Jon Harrop
2007-12-11 2:03 ` Yitzhak Mandelbaum
2007-12-15 21:33 ` Oliver Bandel [this message]
2007-12-16 15:14 ` Jon Harrop
2007-12-10 23:24 ` Jon Harrop
2007-12-09 21:57 ` Oliver Bandel
2007-12-09 22:12 ` Jon Harrop
2007-12-09 22:34 ` Oliver Bandel
2007-12-09 22:16 ` Oliver Bandel
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=1197754414.4764482e09e3f@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@yquem.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