search for: fileaddedcont

...ning”, but the “something was added” is a transient state. Each last file, changes it. The InputGraph knows how to exit a group, but does not know if it should. The Resolver knows which files added content, but does not know which files are in what groups. How about this for InputGraph: void fileAddedContent(File *); // asserts that File* param is the same thing nextFile() last returned File *nextFile(); The Resolver, also tells the InputGraph which files it used. When in a group, the InputGraph keeps a flag for the group of whether it has contributed anything. It starts as false for the first e...

Shankar and I discussed input file handling, and we came up with a design that may greatly simplify the input file handling, while giving more flexibility to developer to support complicated options, such as --{start,end}-group, -z rescan or -z rescan-now. It'd worth pursuing, so here's the idea: 1. We wouldn't probably want to let Resolver to handle the input graph directly, for we

...a > transient state. Each last file, changes it. > > The InputGraph knows how to exit a group, but does not know if it should. > The Resolver knows which files added content, but does not know which > files are in what groups. > > How about this for InputGraph: > > void fileAddedContent(File *); // asserts that File* param is the same > thing nextFile() last returned > File *nextFile(); > > The Resolver, also tells the InputGraph which files it used. When in a > group, the InputGraph keeps a flag for the group of whether it has > contributed anything. It st...