On Tue, Jan 28, 2003 at 01:22:55AM -0600, D. Hageman wrote:
> ...
> 2) The XF86Config file format does what it does very well. It isn't
> necessarily what we are looking for. It also isn't exactly a library that
> one can just use. It is a very custom built parser for a very specific
> purpose. We don't need to re-invent the wheel here.
>
> ...
> No - as stated above it is a custom built parser with very specific
> operating parameters. You can look at it yourself in the XFree86 tree and
> you will see what I mean.
Hmmm. Unfortunate.
Well, on the brighter side, I would say that the XFree config file would
seem to have a simpler parsing style than your average XML document.
Perhaps the DRI config team could do the xfree side a favour, and write an
actual mini-library. Then actually migrate code in the other direction
for once :->
After all, it seems to be a pretty durn simple layout.
It has "only" two basic levels.
At the simplest overview, it only has
Section {sectionname}
Directive {value}
SubSection {subsectionname}
Directive {value}
EndSubSection
EndSection
The irritating bit comes when you add in the Option wildcard.
If you ignore that, you could write a parsing library for it in well under
a weekend. Probably a single day,even.
Well, *I* could, if I had the free time, and actually wanted to spend it on
such an endevour ;-)
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
