From: Jon Loeliger <jdl@freescale.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] DTC: Add support for a C-like #include "file" mechanism.
Date: Thu, 29 Mar 2007 11:02:48 -0500 [thread overview]
Message-ID: <1175184168.32390.275.camel@ld0161-tx32> (raw)
In-Reply-To: <20070329020744.GB16270@localhost.localdomain>
On Wed, 2007-03-28 at 21:07, David Gibson wrote:
> > > > +<INCLUDE>\"[^"\n]*\" {
> > > > + yytext[strlen(yytext) - 1] = 0;
> > > > + if (!push_input_file(yytext + 1)) {
> > > > + /* Some unrecoverable error.*/
> > >
> > > Should be some kind of error message here.
> >
> > Hrm. Yeah.
So I looked, and all the return 0 cases issue specific
errors before returning, so that happens already.
> > Well, it has to come early so that the type is seen
> > prior to the builtin version. But it could be reorganized
> > a bit, I suppose. I was just angling on not cluttering
> > up the lexer proper.
>
> Err... builtin version of what?
I forgot I already separated out the YYLTYPE definition
to handle this issue. Never mind; it's kosher already.
> > Note some people are seeing some compilation problems
> > around the struct field "filenum" that I introduced.
> > I don't see that problem, but a coworker here does,
> > so I am now able to reproduce the issue and am working
> > on a fix. Sorry.
>
> Hrm. Which struct did you add the field to?
And the patch I applied yesterday fixed this YYLTYPE up too.
jdl
next prev parent reply other threads:[~2007-03-29 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 20:18 [PATCH] DTC: Add support for a C-like #include "file" mechanism Jon Loeliger
2007-03-26 13:41 ` Jon Loeliger
2007-03-26 23:10 ` David Gibson
2007-03-28 6:21 ` David Gibson
2007-03-28 17:16 ` Jon Loeliger
2007-03-29 2:07 ` David Gibson
2007-03-29 16:02 ` Jon Loeliger [this message]
2007-03-28 7:05 ` Li Yang-r58472
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1175184168.32390.275.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox