From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org,
Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: [DTC PATCH] Add support for decimal, octal and binary based cell values.
Date: Fri, 16 Feb 2007 08:44:43 +1100 [thread overview]
Message-ID: <1171575883.5644.46.camel@localhost.localdomain> (raw)
In-Reply-To: <E1HHkym-0005u5-HA@jdl.com>
On Thu, 2007-02-15 at 12:05 -0600, Jon Loeliger wrote:
> So, like, the other day "Yoder Stuart-B08248" mumbled:
> >
> > I like to see no space between the d#, h#, etc and the
> > numeric value.
>
> So, that's one of the really nice things about parsers.
> Just do this, then:
>
> d23 = <d#23>; // Just like <d# 23>!
>
> The real question, though, is this: MUST the space between
> 'd#' and '23' be removed so that it is all one token?
> I suppose I could repaint that shed if needed, but I
> don't think it is.
Also, the question is, will the d# affect only the next number or all
the numbers until the next ">" ?
Ben.
next prev parent reply other threads:[~2007-02-15 21:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 17:13 [DTC PATCH] Add support for decimal, octal and binary based cell values Jon Loeliger
2007-02-15 17:30 ` Kumar Gala
2007-02-15 17:49 ` Yoder Stuart-B08248
2007-02-15 18:41 ` Kumar Gala
2007-02-15 22:14 ` David Gibson
2007-02-16 0:04 ` Kumar Gala
2007-02-16 10:23 ` Segher Boessenkool
2007-02-15 17:45 ` Yoder Stuart-B08248
2007-02-15 18:00 ` Olof Johansson
2007-02-15 18:00 ` Yoder Stuart-B08248
2007-02-15 18:02 ` Scott Wood
2007-02-15 18:05 ` Jon Loeliger
2007-02-15 18:10 ` Yoder Stuart-B08248
2007-02-15 21:44 ` Benjamin Herrenschmidt [this message]
2007-02-15 22:12 ` David Gibson
2007-02-15 22:59 ` Jon Loeliger
2007-02-15 22:19 ` David Gibson
2007-02-15 23:43 ` Jon Loeliger
2007-02-15 22:33 ` Dan Malek
2007-02-15 22:57 ` David Gibson
2007-02-15 23:37 ` Dan Malek
2007-02-16 0:09 ` David Gibson
2007-02-16 10:21 ` Segher Boessenkool
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=1171575883.5644.46.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stuart.yoder@freescale.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.