Matthieu Moy <matthieu....@grenoble-inp.fr> writes: > Tanay Abhra <tanay...@gmail.com> writes: > >> On 7/25/2014 2:52 AM, Ramsay Jones wrote: >>> However, I think it you could create a list of <pointer to hash-table >>> entry, string-list index> pairs in the config_set and use that to do >>> the iteration. A bit ugly, but it should work. >> >> Thanks for the advice, that is exactly what I am doing. > > I'd just replace "list" with "array" and use > Documentation/technical/api-allocation-growing.txt. > > But I can't think of a better way.
Presumably this array will reflect the order the source file told us about the keys and their values; I wonder if the <filename, lineno> information we already have can be used (or unified) with it? Is the "when the last variable in a section disappears, make the section header go away, with sensible handling of comments around it" part of this GSoC project? If so, I suspect that the feature would also want to know where things appear in the original file, so this data structure may play a role there, too. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html