From: Sven LUTHER <luther@maxime.u-strasbg.fr>
To: Junbiao Zhang <junzhang@ccrl.nj.nec.com>, caml-list@inria.fr
Subject: Re: forward function definitions
Date: Mon, 14 Jun 1999 12:55:38 +0200 [thread overview]
Message-ID: <19990614125538.B19275@maxime.u-strasbg.fr> (raw)
In-Reply-To: <Pine.GSO.4.10.9906091354050.14576-100000@flame>; from Junbiao Zhang on Wed, Jun 09, 1999 at 02:38:22PM -0400
On Wed, Jun 09, 1999 at 02:38:22PM -0400, Junbiao Zhang wrote:
> Hi,
>
> We're developing a fairly large system with multiple function
> definitions. It's inevitable that some functions may call other functions
> defined later(may not even be recursive calls as in the case of
> Sys.Signal_handle). My question is: how do I solve such a problem which is
> extremely trival in other languages? Thanks.
If the two functions are in different modules, just provide a interface file
for them, and it should work ok but can cause some linker problems.
2 clean way of doing this are :
* use the later called function as a parameter to the first called function :
let register_signals_arg f = Sys.signal Sys.sigalrm (Sys.Signal_handle f)
...
let a sigid = ...
let register_signals = register_signals_arg a
* Or you could define all this in the form of a module functor :
module type XXX = sig val a : id -> ... end
module Make_M (X : XXX) = struct
let register_signals = Sys.signal Sys.sigalrm (Sys.Signal_handle X.a)
end
module ARG = struct
let a sigid = ...
end
module M = Make_M ARG
open M
Friendly,
Sven LUTHER
next prev parent reply other threads:[~1999-06-14 15:49 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 [this message]
1999-06-14 16:17 ` Pierre Weis
1999-06-16 13:03 ` luther sven
1999-06-16 20:55 ` Pierre Weis
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=19990614125538.B19275@maxime.u-strasbg.fr \
--to=luther@maxime.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=junzhang@ccrl.nj.nec.com \
--cc=luther@dpt-info.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