From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: ANN: RASCL's A Simple Configuration Language
Date: Wed, 28 Jun 2006 19:36:03 -0600 [thread overview]
Message-ID: <44A32E83.5020305@gushee.net> (raw)
Here's yet another configuration language--with an OCaml library to
process it, of course.
RASCL came into being after I investigated the Config_file library and
found it overly complex--which may say more about me than about the
library. But at any rate, RASCL, the language, and Rascl, the OCaml
library attempt to be about as simple as possible for both users and
developers, at the expense of some generality.
Here are some of the main features:
* A RASCL file may be just a sequence of keys and values, or it may
be arbitrarily nested.
* Values may be strings, integers, floats, booleans, or lists thereof.
* No OCaml-specific types supported (that's a feature, not a bug ;-)
* Strings need not be quoted unless they contain special characters
or would otherwise be parsed as another type.
* Two interfaces for accessing configs:
- Dict module
- Object system, with a CamlP4 preprocessor to generate objects
and sample config files
BTW, I have attempted to provide thorough documentation for the language
RASCL--in case anyone wants to implement it for other programming
languages. However, I don't have a lot of experience writing language
specifications, and there are probably some errors and ambiguities. I'd
appreciate feedback from any interested and knowledgeable parties.
RASCL and Rascl may be found at: <http://matt.gushee.net/rascl/>
--
Matt Gushee
: Bantam - lightweight file manager : matt.gushee.net/software/bantam/ :
: RASCL's A Simple Configuration Language : matt.gushee.net/rascl/ :
reply other threads:[~2006-06-29 1:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44A32E83.5020305@gushee.net \
--to=matt@gushee.net \
--cc=caml-list@inria.fr \
/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