|
From: Geoff H. <ghu...@ws...> - 2003-01-10 15:38:49
|
It's probably my fault if this didn't end up in the CVS. I'll take a look later this morning. But AFAIK, this is the latest version of the defaults.xml "builder." -Geoff Begin forwarded message: > From: Brian White <bw...@st...> > Date: Sun Nov 10, 2002 08:05:48 PM US/Central > To: lh...@ee... > Cc: htd...@li... > Subject: Re: [htdig-dev] defaults.cc > > At 11:43 11/11/2002, Lachlan Andrew wrote: >> Greetings Brian, >> >> The latest version of defaults.cc that I >> have is at <http://www.ee.mu.oz.au/staff/lha/defaults.cc>. >> It includes all of my earlier changes, plus some >> forward-ported 3.1.6 attributes. > > Well, I ran it through my defaults.xml builder and > ( much to my chagrin! ) it didn't work straight up. > > I have sheepishly attached a slightly adjusted > version of the builder..... > >> On Mon, 11 Nov 2002 10:35, Brian White wrote: >> > At 17:44 8/11/2002, Gabriele Bartolini wrote: >> > > we'd need to change the Configuration.[h,cc] files >> > Those changes are all in the patch I supplied. >> While we're changing Configuration.cc, what do people >> think about issuing a warning if an attribute is not >> found, rather than silently using the "default_value" >> argument? That would remind developers to add the >> attribute to defaults.xml and avoid having default >> values scattered throughout the code... > > On the face of it, I think this is a good idea, but > it would need to be carefully done... > > Brian |