Yes.
On Mon, Jul 22, 2013 at 10:25:09AM -0700, Alex Wang wrote:
> Seems I understand now,
>
> Is that for directing all error messages to corresponding lines in
> "lib/dirs.c.in"?
>
>
> On Mon, Jul 22, 2013 at 10:20 AM, Alex Wang wrote:
>
> > Looks good to me,
> >
> > One question, why do we
Thanks Ben for the explanation,
On Mon, Jul 22, 2013 at 10:37 AM, Ben Pfaff wrote:
> Yes.
>
> On Mon, Jul 22, 2013 at 10:25:09AM -0700, Alex Wang wrote:
> > Seems I understand now,
> >
> > Is that for directing all error messages to corresponding lines in
> > "lib/dirs.c.in"?
> >
> >
> > On Mon
On Mon, Jul 22, 2013 at 10:20:54AM -0700, Alex Wang wrote:
> One question, why do we have the "#line directive" in "lib/dirs.c.in"?
> We have already created "dirs.c" in "lib/automake.mk". What is the
> use of "#line directive" here?
dirs.c gets generated by search-and-replace on dirs.c.in. If th
Seems I understand now,
Is that for directing all error messages to corresponding lines in
"lib/dirs.c.in"?
On Mon, Jul 22, 2013 at 10:20 AM, Alex Wang wrote:
> Looks good to me,
>
> One question, why do we have the "#line directive" in "lib/dirs.c.in"?
> We have already created "dirs.c" in "l
Looks good to me,
One question, why do we have the "#line directive" in "lib/dirs.c.in"?
We have already created "dirs.c" in "lib/automake.mk". What is the
use of "#line directive" here?
Thanks,
On Thu, Jul 18, 2013 at 4:15 PM, Ben Pfaff wrote:
> Signed-off-by: Ben Pfaff
> ---
> lib/dirs.c
