From: jose.kahan@w3.org
Date: Tue Nov 23 1999 - 11:43:09 CST
In our previous episode, Kent Landfield said:
Ah, I didn't know if it was a bug or a design choice :)
[snip]
>
> Warning ... brainstorming...
>
> We could add a boolean variable to struct Config in setup.h that would be
> (currently) used only for list variables. It would be set in PreConfig()
> for each of the lists. When the ConfigAddItem() encounters a list it could
> then check the boolean flag to see if this is the first time a list element
> has been added since the builtin initialization. If so then we would free
> any existing memory, re-initialize the list with the new information and
> set the boolean flag variable to false. Subsequent calls to ConfigAddItem()
> would find the flag off and add the new element to the list as is done now.
>
> Does this sound reasonable ?
Sounds OK to me. The change should go somewhere in ConfigAddItem.
I wonder if you could use the cfg[i].changed flag to do what you're
proposing?
-Jose