Ronald G Minnich wrote: > > extern int regexec _RE_ARGS ((const regex_t *__restrict __preg, > const char *__restrict __string, > size_t __nmatch, > regmatch_t __pmatch[__restrict_arr], > int __eflags)); > > dang, and it's getting a build error too :-) > > Where do the compiler attribute hacks end and the code begin, we wonders?
What bright spark thought the double underscores on the arg names was a good idea. Could be worse. It could be C++ with all those highly readable '<', '>' and '::' sequences. But luckily there's only one array parameter so the error is not that much of a challenge.
