From: Pierre Weis <Pierre.Weis@inria.fr>
To: luther@steed.u-strasbg.fr (luther sven)
Cc: caml-list@inria.fr
Subject: Re: forward function definitions
Date: Wed, 16 Jun 1999 22:55:31 +0200 (MET DST) [thread overview]
Message-ID: <199906162055.WAA22149@pauillac.inria.fr> (raw)
In-Reply-To: <19990616150347.C6385@steed.u-strasbg.fr> from "luther sven" at Jun 16, 99 03:03:47 pm
> Ah, but you can define a wrapper immediately following the definition of the forwarder function :
>
> let f for () = ...
>
> ...
>
> let for ... = ...
> let true_f = f for
>
> Friendly,
>
> Sven LUTHER
Yes you can do so, but you once again get the same polymorphism
problem:
1) If for is used polymorphically in the body of f you're dead.
2) true_f will be monomorphic as well, unless you eta-expand it as in:
let true_f () = f for ()
PS: for is indeed a keyword, and this identifier cannot be used as a
regular argument or function name ...
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://cristal.inria.fr/~weis/
next prev parent reply other threads:[~1999-06-16 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-09 18:38 Junbiao Zhang
1999-06-14 10:55 ` Sven LUTHER
1999-06-14 16:17 ` Pierre Weis
1999-06-16 13:03 ` luther sven
1999-06-16 20:55 ` Pierre Weis [this message]
1999-06-17 8:46 ` Sven LUTHER
1999-06-14 10:34 Toby Moth
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=199906162055.WAA22149@pauillac.inria.fr \
--to=pierre.weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=luther@steed.u-strasbg.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