search for: currentresolverst

...re being fulfilled by a,b,c,a,b,c…, but how does the resolver know that the files are repeating, to know to tell the InputGraph to move on? nextFile could pass the current resolver state at the time when its called, the linkingcontext can return the next file to be processed as below :- nextFile(currentResolverState) :- a) Returns the next file if the current node is not a group node b) Returns the next file in the group node, if the current node is a group node and the resolver state states undefined /weak / shared library atoms were added. c) Returns the start file in the group node, if the resolver st...

...>>> <shankare at codeaurora.org> wrote: >>>> nextFile could pass the current resolver state at the time when its >>>> called, the linkingcontext can return the next file to be processed >>>> as below :- >>>> >>>> nextFile(currentResolverState) :- >>>> >>>> a) Returns the next file if the current node is not a group node >>>> b) Returns the next file in the group node, if the current node is >>>> a group node and the resolver state states undefined /weak / shared >>>> libra...

...he group provided any more content. On Sep 20, 2013, at 3:42 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > nextFile could pass the current resolver state at the time when its called, the linkingcontext can return the next file to be processed as below :- > > nextFile(currentResolverState) :- > > a) Returns the next file if the current node is not a group node > b) Returns the next file in the group node, if the current node is a group node and the resolver state states undefined /weak / shared library atoms were added. > c) Returns the start file in the group node,...

...k Kledzik wrote: > On Sep 20, 2013, at 3:42 PM, Shankar Easwaran > <shankare at codeaurora.org> wrote: >> nextFile could pass the current resolver state at the time when its called, the linkingcontext can return the next file to be processed as below :- >> >> nextFile(currentResolverState) :- >> >> a) Returns the next file if the current node is not a group node >> b) Returns the next file in the group node, if the current node is a group node and the resolver state states undefined /weak / shared library atoms were added. >> c) Returns the start file in t...

...ankare at codeaurora.org> wrote: >>>>> nextFile could pass the current resolver state at the time when >>>>> its called, the linkingcontext can return the next file to be >>>>> processed as below :- >>>>> >>>>> nextFile(currentResolverState) :- >>>>> >>>>> a) Returns the next file if the current node is not a group node >>>>> b) Returns the next file in the group node, if the current node is >>>>> a group node and the resolver state states undefined /weak / >>>&...

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

...42 PM, Shankar Easwaran >> <shankare at codeaurora.org> wrote: >>> nextFile could pass the current resolver state at the time when its >>> called, the linkingcontext can return the next file to be processed >>> as below :- >>> >>> nextFile(currentResolverState) :- >>> >>> a) Returns the next file if the current node is not a group node >>> b) Returns the next file in the group node, if the current node is a >>> group node and the resolver state states undefined /weak / shared >>> library atoms were added....

Rui, I like this in general, but have a few questions. On Sep 20, 2013, at 2:30 PM, Rui Ueyama <ruiu at google.com> wrote: > 2. We would instead add a new method nextFile() to LinkingContext, which returns a new file from which Resolver should try to resolve undefined symbols. Resolver wouldn't handle the input graph at all. Instead, Resolver calls nextFile() repeatedly to link

...2 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: >>>>>> nextFile could pass the current resolver state at the time when its called, the linkingcontext can return the next file to be processed as below :- >>>>>> >>>>>> nextFile(currentResolverState) :- >>>>>> >>>>>> a) Returns the next file if the current node is not a group node >>>>>> b) Returns the next file in the group node, if the current node is a group node and the resolver state states undefined /weak / shared library atoms...

...ent. > > > On Sep 20, 2013, at 3:42 PM, Shankar Easwaran <shankare at codeaurora.org> > wrote: > > nextFile could pass the current resolver state at the time when its > called, the linkingcontext can return the next file to be processed as > below :- > > nextFile(currentResolverState) :- > > a) Returns the next file if the current node is not a group node > b) Returns the next file in the group node, if the current node is a group > node and the resolver state states undefined /weak / shared library atoms > were added. > c) Returns the start file in the gro...