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: David MENTRE <david.mentre@gmail.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Looking for a configuration file library
Date: Wed, 28 Sep 2005 09:55:50 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0509280938540.28672@shell4.speakeasy.net> (raw)
In-Reply-To: <1127925464.7743.71.camel@rosella>

On Thu, 29 Sep 2005, skaller wrote:
> On Wed, 2005-09-28 at 08:15 -0700, brogoff wrote:
>
> > > [1] Even if, in the long term, I want to remove noweb in order to use
> > > a literate programing style relying on language source code, like
> > > ocamldoc.
> >
> > That is exactly what I wish they had done.
>
> Why?

Getting off topic, but since you ask...

Because, Borg like, I wish to integrate whatever source code I grab into my
own code base, perhaps modifying it, and I don't wish to add yet another layer
of perl scripts and extra  weird tools into my flow. I'd rather Lua-ML be just
like the libraries that are distributed with OCaml.

Also, I don't believe programs are enough like books that LP is worth
adopting. In short I'm an LP unbeliever (behead me!).

> Is there problem with running noweb to extract the source?

That's the first step, then you need to get the comments right. And there
was a problem with yacc stuff, but nothing beyond grunt work, like I said.

> Or is there a problem editing noweb files?

I don't want to edit noweb files. I'm willing to do it once to undo the hard
work the authors put into it, but then it's goodbye to all that.

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.

-- Brian


  reply	other threads:[~2005-09-28 16:55 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 [this message]
2005-09-29  3:33           ` skaller
2005-09-29  4:02             ` brogoff
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.0509280938540.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).