From owner-freebsd-arch Sun Jul 16 13:35:12 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mail.integratus.com (miami.integratus.com [63.209.2.83]) by hub.freebsd.org (Postfix) with SMTP id 594CF37C7CD for ; Sun, 16 Jul 2000 13:35:04 -0700 (PDT) (envelope-from jar@integratus.com) Received: (qmail 18365 invoked from network); 16 Jul 2000 20:34:57 -0000 Received: from kungfu.integratus.com (HELO integratus.com) (172.20.5.168) by tortuga1.integratus.com with SMTP; 16 Jul 2000 20:34:57 -0000 Message-ID: <39721C71.FD6CB5B2@integratus.com> Date: Sun, 16 Jul 2000 13:34:57 -0700 From: Jack Rusher Organization: Integratus X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nik Clayton , freebsd-arch@FreeBSD.ORG Subject: Re: XML configurations References: <20000712144510.A11316@ywing.creative.net.au> <200007130537.WAA29614@apollo.backplane.com> <20000714112117.D17372@ywing.creative.net.au> <20000714053540.A30847@holly.calldei.com> <20000714124327.A64283@mithrandr.moria.org> <396F531F.BBE0D54E@integratus.com> <20000715232447.A21066@kilt.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > > > etc. XML seems like the right answer for this. > > Sort of. You still need to write the DTDs, which is the harder part. The DTD syntax is awfully straight forward, and it is certainly easier to write a DTD (and validating schema) than it is to write a custom parser from scratch (even with lex and yacc). The XML/DTD approach is designed for a constrained problem domain that more closely matches the needs of most configuration files than the generalist approach of lex and yacc. Yes, this statement does mean that I would be willing to contribute some time to getting DTDs written for new file formats. -- Jack Rusher, Senior Engineer | mailto:jar@integratus.com Integratus, Inc. | http://www.integratus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message