From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux-Kernel list <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net
Cc: Roman Zippel <zippel@linux-m68k.org>
Subject: Yet another config language...
Date: Thu, 21 Feb 2002 08:51:08 -0500 [thread overview]
Message-ID: <3C74FB4C.280DBE53@mandrakesoft.com> (raw)
I have been pointed to eCos's config language, which seems to have a lot
of desireable properties: it seems compatible with our needs (no global
dependencies, all info in one file, just-plop-down-driver.conf like),
it's implemented, fully documented, and most importantly (IMO),
it looks possible to modify their config parser to read CML1, which
allows us to (a) prove the new design and (b) transition slowly.
Language overview and some quick samples:
http://sources.redhat.com/ecos/docs-latest/cdl/language.html
Language reference:
http://sources.redhat.com/ecos/docs-latest/cdl/reference.html
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
reply other threads:[~2002-02-21 13:51 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=3C74FB4C.280DBE53@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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