From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id XAA25493; Thu, 20 May 2004 23:41:46 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id XAA25320 for ; Thu, 20 May 2004 23:41:45 +0200 (MET DST) Received: from plover.csun.edu (plover.csun.edu [130.166.1.24]) by concorde.inria.fr (8.12.10/8.12.10) with ESMTP id i4KLfiSH010321 for ; Thu, 20 May 2004 23:41:44 +0200 Received: from puffin.csun.edu (puffin.csun.edu [130.166.1.21]) by plover.csun.edu (MOS 3.4.6-GR) with ESMTP id BDV75219; Thu, 20 May 2004 14:41:41 -0700 (PDT) Received: from [130.166.10.91] (s010n091.csun.edu [130.166.10.91]) by puffin.csun.edu (MOS 3.4.4-GR) with ESMTP id BTT64337 (AUTH eric); Thu, 20 May 2004 14:41:24 -0700 (PDT) In-Reply-To: <200405202204.27693.jdh30@cam.ac.uk> References: <20040519172442.30413.qmail@web14522.mail.yahoo.com> <200405201837.25278.jdh30@cam.ac.uk> <7BF7E098-AA9C-11D8-A7CF-000A95A1E69A@csun.edu> <200405202204.27693.jdh30@cam.ac.uk> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <71024598-AAA6-11D8-A7CF-000A95A1E69A@csun.edu> Content-Transfer-Encoding: 7bit Cc: caml-list@inria.fr From: Eric Stokes Subject: Re: [Caml-list] Large projects in OCaml Date: Thu, 20 May 2004 14:41:24 -0700 To: Jon Harrop X-Mailer: Apple Mail (2.613) X-Miltered: at concorde with ID 40AD2618.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 2004:99 immune:99 mylib:01 bug:01 faq:01 faq:01 beginner's:01 beginners:01 bin:01 linked:01 inconsistent:01 caml-bugs:01 ocaml:01 ocaml:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk 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