From: skaller <skaller@users.sourceforge.net>
To: Richard Jones <rich@annexia.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: int hash
Date: 15 Jul 2004 07:29:27 +1000 [thread overview]
Message-ID: <1089840567.29648.533.camel@pelican.wigram> (raw)
In-Reply-To: <20040714144651.GA26850@redhat.com>
On Thu, 2004-07-15 at 00:46, Richard Jones wrote:
> On Thu, Jul 15, 2004 at 12:27:50AM +1000, skaller wrote:
> > For some things .. not necessarily this one .. DynArray
> > would be great .. but it creates a dependence on an
> > unstable third party LGPL'd library. I can neither
> > lift the relevant code (due to the licence),
> > nor lightly require my clients install that library
> > just to build my product. [I have seriously considered
> > requiring ExtLib]
>
> I almost consider ExtLib to be part of "standard OCaml", along with
> PCRE. It's easier just to have both installed whenever I set up a new
> machine with OCaml, than to have to worry about writing the extra code
> to simulate functionality already in ExtLib.
>
That is reasonable for an Ocaml developer (which I am),
but not as clearly reasonable for a *client* of my
code who is probably not. I feel the need to supply
a system consisting of the smallest number of
separately installable components for obvious
reasons: every dependence on a third party component
makes my package fragile. For example, I'd like it
to install on Win32 native.. I don't have control
of third party packages so how do i respond when
a client has a problem?
Note the problem *isn't* the quality of the third
party code! Its sure to be better than mine :)
I have a client that installs my package on 5 different
platforms (his product is a multi-platform game, it runs
on OSX, Linux[both PC and XBox], OS9, Cygwin and Mingw
at present).
This problem may be substantially corrected by GODI
because it provides a *unified* installation system.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
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-07-14 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 9:33 [Caml-list] " skaller
2004-07-14 12:16 ` [Caml-list] " Julian Brown
2004-07-14 14:27 ` skaller
2004-07-14 14:46 ` Richard Jones
2004-07-14 21:29 ` skaller [this message]
2004-07-14 15:32 ` henri dubois-ferriere
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=1089840567.29648.533.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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).