From: Eric Stokes <eric.stokes@csun.edu>
To: Jon Harrop <jdh30@cam.ac.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Large projects in OCaml
Date: Thu, 20 May 2004 14:41:24 -0700 [thread overview]
Message-ID: <71024598-AAA6-11D8-A7CF-000A95A1E69A@csun.edu> (raw)
In-Reply-To: <200405202204.27693.jdh30@cam.ac.uk>
On May 20, 2004, at 2:04 PM, Jon Harrop wrote:
> On Thursday 20 May 2004 21:30, Eric Stokes wrote:
>> ...
>> No, that is the case with dynamic linking, not static linking. The
>> only
>> issue with
>> static linking and commercial stuff is that your patches are likely to
>> be much bigger.
>> However the good thing about it is that your code is fairly immune to
>> dynamic library
>> changes on the client machine.
>
> Would my users not keep getting unavoidable "The files blah.cmi and
> mylib.cmi
> make inconsistent assumptions over interface Blah"?
>
If it is a library that you maintain you would need to send a new .cmi
file with each
new version of the library. But an application linked to your library
would not be effected
by this change in any way unless the application writer recompiled the
application against
the new version of the library. There is no link phase (except linking
to external c libraries)
at the start of an Ocaml program. The application binary contains a
copy of all the Ocaml code
ever used by the program, including library code.
> Cheers,
> Jon.
>
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives:
> http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ:
> http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-05-20 21:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 17:24 ramu ramamurthy
2004-05-19 21:33 ` Jon Harrop
2004-05-19 23:04 ` David J. Trombley
2004-05-20 16:31 ` Eric Stokes
2004-05-20 17:37 ` Jon Harrop
2004-05-20 20:30 ` Eric Stokes
2004-05-20 21:04 ` Jon Harrop
2004-05-20 21:41 ` Eric Stokes [this message]
2004-05-21 11:28 ` Jon Harrop
2004-05-21 12:49 ` Ville-Pertti Keinonen
2004-05-21 16:27 ` Jon Harrop
2004-05-24 3:07 ` Jacques GARRIGUE
2004-05-24 5:20 ` skaller
2004-05-24 12:14 ` Jacques GARRIGUE
2004-05-24 13:54 ` skaller
2004-05-24 14:20 ` Xavier Leroy
2004-05-24 16:48 ` Alex Baretta
2004-05-24 17:38 ` brogoff
2004-05-25 5:25 ` Alan Schmitt
2004-05-24 19:24 ` skaller
2004-05-24 19:52 ` Brandon J. Van Every
2004-05-24 14:20 ` Daniel Bünzli
2004-05-24 19:34 ` skaller
2004-05-24 16:49 ` james woodyatt
2004-05-19 21:38 ` Richard Jones
2004-05-20 8:46 ` skaller
2004-05-20 11:56 ` [Caml-list] A problem with nan sejourne kevin
2004-05-20 20:42 ` Jon Harrop
2004-05-20 22:24 ` David J. Trombley
2004-05-20 22:45 ` Damien Doligez
2004-05-20 13:10 ` [Caml-list] Large projects in OCaml Jon Harrop
2004-05-20 16:23 ` skaller
2004-05-20 6:35 ` David Monniaux
2004-05-20 7:17 ` Dustin Sallings
2004-05-25 7:26 Mattias Waldau
2004-05-25 19:07 ` Richard Jones
2004-05-25 19:54 ` Evan Martin
2004-05-26 6:57 ` skaller
2004-05-26 8:09 ` Richard Jones
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=71024598-AAA6-11D8-A7CF-000A95A1E69A@csun.edu \
--to=eric.stokes@csun.edu \
--cc=caml-list@inria.fr \
--cc=jdh30@cam.ac.uk \
/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).