Geoff Hutchison <[EMAIL PROTECTED]> writes: > >The problem is you want to be able to override attributes that were > >defined previously, in an include file for example. I'd favour a > >different syntax for appending to an already defined attribute, > >e.g.: > > bad_extensions += .pdf > > Right. Plus this sort of change will be a bit easier to do now that > the guts of the config parser was re-written by Vadim in bison/flex. Of course if a future version incorporates an XML parser, using XML for the config file would be a natural, and one less parser you'd need in the code. It may also make sense to remove config defaults from the compiled code and put them into an external "system defaults" file, which then gets included by each of the user's need-specific - or "dig session" - config files. Then they can directly change the "system defaults" to reflect the site wide configuration and use the other config files to set parameters for a specific dig (database, starting URL, etc.). This may leave htdig without a definition for a needed directive if the "system defaults" file is mangled or missing, but it could just dump an error message and quit, much as Apache would. It's a trade off between added flexibility and understandability vs. the need to have yet another external file present for proper operation. -Tom -- Tom Metro Venture Logic [EMAIL PROTECTED] Newton, MA, USA ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You'll receive a message confirming the unsubscription.
