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 WAA21432; Thu, 20 May 2004 22:30:14 +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 WAA21468 for ; Thu, 20 May 2004 22:30:12 +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 i4KKUBSH002837 for ; Thu, 20 May 2004 22:30:11 +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 BDV68181; Thu, 20 May 2004 13:30:09 -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 BTT51255 (AUTH eric); Thu, 20 May 2004 13:30:08 -0700 (PDT) In-Reply-To: <200405201837.25278.jdh30@cam.ac.uk> References: <20040519172442.30413.qmail@web14522.mail.yahoo.com> <200405192104.29698.jdh30@cam.ac.uk> <142FF679-AA7B-11D8-A7CF-000A95A1E69A@csun.edu> <200405201837.25278.jdh30@cam.ac.uk> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7BF7E098-AA9C-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 13:30:07 -0700 To: Jon Harrop X-Mailer: Apple Mail (2.613) X-Miltered: at concorde with ID 40AD1553.002 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 libs:01 statically:01 immune:99 bug:01 faq:01 faq:01 beginner's:01 beginners:01 bin:01 linked:01 caml-bugs:01 ocaml:01 ocaml:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On May 20, 2004, at 10:37 AM, Jon Harrop wrote: > On Thursday 20 May 2004 17:31, Eric Stokes wrote: >> ... >> There is no issue at all distributing object code. You do not have to >> distribute source. >> The issue is, that the language does not support creating shared >> libraries written in Ocaml >> (though it can link to C shared libs), so all the object code you >> distribute will be statically >> linked. If you are planning to sell a library written in Ocaml, it >> will >> necessarily be a static >> library. For application code, static linking is probably preferred in >> some cases, and >> acceptable in most. > > But if any other objects which my objects depend upon get changed then > my > object code will stop working. > 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. > 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