Re: code coverage patch
От
Korry Douglas
Тема
Re: code coverage patch
Дата
Msg-id
3F71903C-C784-4678-BDA7-32A46B2D9DFC@enterprisedb.com
Ответ на
Re: code coverage patch (Peter Eisentraut)
Список
Дерево обсуждения
code coverage patch Michelle Caisse <Michelle.Caisse@Sun.COM>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Korry Douglas <korry.douglas@enterprisedb.com>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Tom Lane <tgl@sss.pgh.pa.us>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Tom Lane <tgl@sss.pgh.pa.us>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Gregory Stark <stark@enterprisedb.com>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Alvaro Herrera <alvherre@commandprompt.com>
Re: code coverage patch Michelle Caisse <Michelle.Caisse@Sun.COM>
Re: code coverage patch Peter Eisentraut <peter_e@gmx.net>
Re: code coverage patch Gregory Stark <stark@enterprisedb.com>
Re: code coverage patch Alvaro Herrera <alvherre@commandprompt.com>
> The problem with those files is that the source file contains lines > like this: > > #line 1042 "y.tab.c" > > but that source file does not exist, as it is renamed to gram.c. > > We could fix that in one of two ways: > > 1) Use bison's -o option to put the output file in the right place > directly, > if we are dealing with bison (and don't bother to support code > coverage > analysis with other yaccs), or > > 2) Run a pattern replacement across the grammar output files as > their are > renamed. Why not use the %output directive in the grammar file instead; that way you don't need to add any special flags to the Makefile. -- Korry
В списке pgsql-hackers по дате отправления