On Fri, Mar 18, 2011 at 16:17, Nicola Pero
<nicola.p...@meta-innovation.com> wrote:
>
>>> + /* cp/parser.h gives gt-cp-parser.h for cp/parser.c ! */
>>> + { DIR_PREFIX_REGEX "cp/parser\\.h$",
>>> + REG_EXTENDED, NULL_REGEX,
>>> + "gt-cp-parser.h", "cp/parser.c", NULL_FRULACT },
>>
>> But cp/parser.c also gets its own gt-cp-parser.h. Won't they
>> conflict? Doesn't this mean that cp/parser.h should be renamed to
>> something else? (say cp/cp-parser.h).
>
> My understanding is that, with that rule, GC generated code from
> cp-parser.h will end up into gt-cp-parser.h, together with the code
> generated from cp-parser.c. gengtype basically runs once for all
> files, so has no problem putting GC generated code from multiple
> input files into the same output file.
OK, thanks.
I'm OK with the patch, but please wait for a specific approval from
Laurynas. I'm not sufficiently familiar with this code to give final
approval.
Diego.
