On Sat, Mar 28, 2015 at 5:38 PM, Ted Unangst wrote:
> Renato Westphal wrote:
>> > +#include
>> > #include
>
>> "#include ",
>> "#include ",
>
>> If you include the stdlib header in the .y file you will end up with
>> two includes for the same header in the .c file.
>
> Looks lik
Renato Westphal wrote:
> > +#include
> > #include
> "#include ",
> "#include ",
> If you include the stdlib header in the .y file you will end up with
> two includes for the same header in the .c file.
Looks like we're already including string.h twice. Probably makes sense
to
On Sat, Mar 28, 2015 at 09:42:00AM -0300, Renato Westphal wrote:
> I don't think that this is necessary. Yacc includes a skeleton C code
> when generating a parser from a grammar specification file (.y) and
> the stdlib header is in there:
>
> char *banner[] =
> {
> "#include ",
>
2015-03-28 8:56 GMT-03:00 Fabian Raetz :
> Hi tech@,
>
> should the stdlib.h header be included in parse.y files when calloc(3)
> is used?
>
> Regards,
> Fabian
>
>
> From ce8307e0bc7541b88a9a9bf949f6585adef46bb6 Mon Sep 17 00:00:00 2001
> From: Fabian Raetz
> Date: Sat, 28 Mar 2015 12:44:32 +0100
Hi tech@,
should the stdlib.h header be included in parse.y files when calloc(3)
is used?
Regards,
Fabian
>From ce8307e0bc7541b88a9a9bf949f6585adef46bb6 Mon Sep 17 00:00:00 2001
From: Fabian Raetz
Date: Sat, 28 Mar 2015 12:44:32 +0100
Subject: [PATCH] include stdlib.h because of calloc(3) usag
