Re: tight-scope check confusion

2013-11-13 Thread Reuben Thomas
On 13 November 2013 19:20, Jim Meyering wrote: > On Wed, Nov 13, 2013 at 10:44 AM, Reuben Thomas wrote: > > On 11 November 2013 14:30, Jim Meyering wrote: > >> > >> Glad you found it. > >> If you can find a good way to document it, I'd appreciate a patch. > > > > > > I can think of nothing bett

Re: tight-scope check confusion

2013-11-13 Thread Jim Meyering
On Wed, Nov 13, 2013 at 10:44 AM, Reuben Thomas wrote: > On 11 November 2013 14:30, Jim Meyering wrote: >> >> Glad you found it. >> If you can find a good way to document it, I'd appreciate a patch. > > > I can think of nothing better than a note in the source, by whoever wrote > it, so it reflec

Re: tight-scope check confusion

2013-11-13 Thread Reuben Thomas
On 11 November 2013 14:30, Jim Meyering wrote: > Glad you found it. > If you can find a good way to document it, I'd appreciate a patch. > I can think of nothing better than a note in the source, by whoever wrote it, so it reflects their intention rather than my half-baked guesses. -- http://

Re: tight-scope check confusion

2013-11-11 Thread Jim Meyering
On Thu, Nov 7, 2013 at 9:52 AM, Reuben Thomas wrote: > On 7 November 2013 14:55, Jim Meyering wrote: >> >> Can you investigate, e.g., instrumenting those rules to see what's >> happening (then I don't have to ask for instructions on how to >> reproduce :-), for example, by, inserting "| tee /tmp/

Re: tight-scope check confusion

2013-11-07 Thread Reuben Thomas
On 7 November 2013 14:55, Jim Meyering wrote: > Can you investigate, e.g., instrumenting those rules to see what's > happening (then I don't have to ask for instructions on how to > reproduce :-), for example, by, inserting "| tee /tmp/1" or similar in > piplelines to see what intermediate result

Re: tight-scope check confusion

2013-11-07 Thread Jim Meyering
On Wed, Nov 6, 2013 at 4:54 PM, Reuben Thomas wrote: > I turned on tight-scope by pointing it at a directory with a library in. > > To start with, it (somewhat confusingly) tells me that all my API functions > should be static. It doesn't seem to have the option to say they should be > extern. Thi