From: David Gibson <david@gibson.dropbear.id.au>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: New U-boot image format
Date: Fri, 21 Dec 2007 11:17:47 +1100 [thread overview]
Message-ID: <20071221001747.GE2665@localhost.localdomain> (raw)
In-Reply-To: <476AEF2A.6090805@freescale.com>
On Thu, Dec 20, 2007 at 04:39:38PM -0600, Scott Wood wrote:
> Marian Balakowicz wrote:
>> I was thinking of a syntax that would be similar to regular data
>> sections which are enclosed in [] braces. Something like:
>> prop = {/path/to/file};
>
> This one overloads {} based primarily on whether there's an equal sign
> before it... a bit icky. Plus, sooner or later we'll run out of special
> characters to assign meaning to, and we'll become Perlish in the process.
> :-)
Indeed. Plus I'd liked to keep { } consistently for delimiting
lexical contexts which will accept node or property names without
quoting.
Plus you can't even count on the { being after an =, because you could have:
prop = "a string followed by", {/a/file};
> I went with text-between slashes as it's an already-established keyword
> marker.
>
>> or prop = [file:/path/to/file];
>
> This is ambiguous; file: will be scanned as a label unless we give
> precedence to it as a keyword, and I don't think we want to go down the
> path of reserved words when we have other mechanisms available to separate
> the namespaces.
And it's gratuitously similar to bytestring notation.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-12-21 0:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 16:18 [U-Boot-Users] RFC: New U-boot image format Marian Balakowicz
2007-12-11 16:32 ` [U-Boot-Users] RFC: New U-boot image format - open issues Marian Balakowicz
2007-12-11 19:23 ` [U-Boot-Users] RFC: New U-boot image format Jerry Van Baren
2007-12-11 22:23 ` Wolfgang Denk
2007-12-12 12:38 ` Jerry Van Baren
2007-12-13 22:59 ` Marian Balakowicz
2007-12-13 22:41 ` Marian Balakowicz
2007-12-14 6:17 ` Wolfgang Denk
2007-12-14 21:44 ` T Ziomek
2007-12-19 14:26 ` Marian Balakowicz
2007-12-20 0:50 ` David Gibson
2007-12-20 16:41 ` Scott Wood
2007-12-20 22:25 ` Marian Balakowicz
2007-12-20 22:39 ` Scott Wood
2007-12-21 0:17 ` David Gibson [this message]
2007-12-18 15:17 ` Timur Tabi
2007-12-18 15:33 ` Jerry Van Baren
2007-12-18 15:36 ` Timur Tabi
2007-12-18 16:12 ` Wolfgang Denk
2007-12-18 16:17 ` Timur Tabi
2007-12-18 19:42 ` Wolfgang Denk
2007-12-18 19:47 ` Timur Tabi
2007-12-18 20:11 ` Wolfgang Denk
2007-12-18 20:18 ` Timur Tabi
2007-12-19 14:07 ` Marian Balakowicz
2007-12-20 19:42 ` Wolfgang Denk
2007-12-21 15:04 ` Marian Balakowicz
2007-12-21 15:17 ` Wolfgang Denk
2007-12-21 15:39 ` Marian Balakowicz
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=20071221001747.GE2665@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=u-boot@lists.denx.de \
/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.