caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: brogoff <brogoff@speakeasy.net>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list <caml-list@inria.fr>, David MENTRE <david.mentre@gmail.com>
Subject: Re: [Caml-list] Looking for a configuration file library
Date: Wed, 28 Sep 2005 21:02:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0509282035530.28672@shell4.speakeasy.net> (raw)
In-Reply-To: <1127964804.20162.36.camel@rosella>

On Thu, 29 Sep 2005, skaller wrote:
> That I understand. Though note: noweb is written in Icon (under debian
> noweb package requires iconx package .. that's the end, two binaries).

You don't need Icon to untangle the Lua-ML sources, and build. Perl and
make and all of that nonstandard stuff that runs on every Unix. I had no
problems on vanilla solaris and RH linux sans Icon.

[...snip...]

> Oh yes, you have a problem: if you manually run noweb and fiddle
> the result, then include that in your own product (which is what
> I do all the time with 3pl software) then you have two SERIOUS
> problems:
>
> (a) you can't easily synchronise with the upstream author

That's the problem.

> (b) you have the usual Licence problem, you whole project
> is now probably a 'derived work'

Public domain.

> > Back to config files. Other languages like Python and Scheme could also be used
> > as configuration files, but Lua is especially suitable when "non programmers"
> > are writing the config scripts.
>
> I doubt that. I'm a programmer, and I spent some time with Lua.
> Simple assignments in Lua are the same as Python:
>
> x = 1
> y = "Hello"
>
> Anything more complex is HARD, and much harder in Lua than

No. It is easy, and I have (admittedly subjective) data from dozens
of nonprogrammer engineers who use it, who formerly wrote config
files in OCaml. So, forgive me if I don't take your word for it, but rather
take theirs.

Much config file data is tabular, and Lua has built in hash tables.

> I actually looked at Lua as a replacement for Python
> to control configuration but threw it out. I am very happy
> now, sticking with Python

I'm happy that you're happy!

> In the end, I would have to recommend using a pure Ocaml
> solution.. because if your Ocaml code embeds native Lua,
> then you need your clients who are 'building from source'
> to have a C compiler to compile Lua.. and you need to
> provide build scripts to do it .. and .. its all a huge
> mess.

Perhaps you need to carefully read every line of my reply to David Mentre,
or, even better, download Lua-ML and give it a try. There is a reason it is
called Lua-ML (hint: it is entirely written in OCaml, no C/C++/Java/Felix!).

> Ocaml is much easier to build .. except that people
> insist on using 'findlib' and INRIA insists on NOT
> supplying it as part of Ocaml. It's an old problem.
> Sigh. GODI and Debian solve these problems entirely .. but they're
> very heavy weight.

I agree that the packaging issue is a big problem.

One of the reasons I prefer OCaml to it's competitors is that it works well
with a Unix style tool chain. If I used Windows, I might feel differently.

-- Brian


  reply	other threads:[~2005-09-29  4:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 13:09 David MENTRE
2005-09-27 13:23 ` [Caml-list] " Bruno De Fraine
2005-09-27 16:26   ` Samuel Mimram
2005-09-28  6:59     ` David MENTRE
2005-09-28  7:06       ` Maxence Guesdon
2005-09-27 17:02 ` brogoff
2005-09-28  7:06   ` David MENTRE
2005-09-28 15:15     ` brogoff
2005-09-28 16:37       ` skaller
2005-09-28 16:55         ` brogoff
2005-09-29  3:33           ` skaller
2005-09-29  4:02             ` brogoff [this message]
2005-09-29  7:24         ` Christian Lindig
2005-09-28 15:40     ` skaller
2005-10-05 10:16 ` 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=Pine.LNX.4.58.0509282035530.28672@shell4.speakeasy.net \
    --to=brogoff@speakeasy.net \
    --cc=caml-list@inria.fr \
    --cc=david.mentre@gmail.com \
    --cc=skaller@users.sourceforge.net \
    /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).