the config file parsing stuff

[Alan Coopersmith]

Chuck Robey wrote:
> Alan Coopersmith wrote:
>> Chuck Robey wrote:
>>> Any of these sound good?  I'd hate to see the work go to waste, although I
>>> suppose the possibility exists that a write on this topic DOES exist somewhere.
>>>  In that case, I'd like a pointer and I'll be thankfully quiet on the subject.
>> The only documentation I know is in the XFree86 DDX layer Design doc
>> in hw/xfree86/doc/sgml/DESIGN.sgml, but I'm not sure how up to date
>> it is, and it could at least use a good review if not some serious
>> editing/updating/expanding.
> 
> 
> I saw that, it seemed to me to be totally about the print server, at least,

That doesn't sound like anything under hw/xfree86/doc - I'd be shocked to see
any documentation there about Xprint.   Are you sure you're looking at the right
document?

The one I see in hw/xfree86/doc/sgml/DESIGN.sgml in the Xorg server source tree
is titled "XFree86 server 4.x Design (DRAFT)" (and since Xorg started with the
XFree86 4.x design, most of it still applies to Xorg).

> that's what the postscript file I saw was about ... nothing whatever about how
> to parse the config file (or, the other thing I will be on about before I feel I
> have the entire enchilada, which is the RIGHT way to print crud into the xorg
> log file in /var/log). 

It documents the calls drivers & other loadable Xorg modules can make to get
data out of the configuration info the server either parsed from xorg.conf
or autodetected.   For instance the section "Config file ``Option'' entries"
documents how drivers can call xf86FindOption*() and similar functions to
get the Option entries from xorg.conf for their driver section.

-- 
	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering