search for: tre_regcomp

...17 21:37, peter dalgaard wrote: > As you're dying in an else clause, a previous if () must contain the clue. Unfortunately not necessarily the matching one. > > My guess is that your TRE library is broken. The line should have matched the RE "regline" defined as > > tre_regcomp(&regline, "^[^:]+:[[:blank:]]*", REG_EXTENDED); > ...and used here: > if(tre_regexecb(&regline, line, 1, regmatch, 0) == 0) { > > but apparently does not. int tre_regcomp(regex_t *preg, const char *regex, int cflags) { return tre_regncomp(preg, rege...

On 2015-12-17 19:30, peter dalgaard wrote: > Presumably the file in question is one of > > Peter-Dalgaards-MacBook-Air:BUILD pd$ grep -r "^Package: tools" * > library/tools/DESCRIPTION:Package: tools > src/library/tools/DESCRIPTION:Package: tools > > so the first thing I'd do is to have a good look at those files and see if they got somehow corrupted. > >

...} > } > ... more lines to go... > As you're dying in an else clause, a previous if () must contain the clue. Unfortunately not necessarily the matching one. My guess is that your TRE library is broken. The line should have matched the RE "regline" defined as tre_regcomp(&regline, "^[^:]+:[[:blank:]]*", REG_EXTENDED); ...and used here: if(tre_regexecb(&regline, line, 1, regmatch, 0) == 0) { but apparently does not. > Thanks for the assistance! > > Michael -- Peter Dalgaard, Professor, Center for Statistics, Copenha...

...lines to go... >> > > As you're dying in an else clause, a previous if () must contain the clue. Unfortunately not necessarily the matching one. > > My guess is that your TRE library is broken. The line should have matched the RE "regline" defined as > > tre_regcomp(&regline, "^[^:]+:[[:blank:]]*", REG_EXTENDED); > ...and used here: > if(tre_regexecb(&regline, line, 1, regmatch, 0) == 0) { > > but apparently does not. > > > >> Thanks for the assistance! >> >> Michael > > -- &...