From: Thierry Reding <thierry.reding@avionic-design.de>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] man: Fix typo and use $() for make expressions
Date: Mon, 21 Jan 2013 07:52:54 +0100 [thread overview]
Message-ID: <20130121065254.GA15508@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <CANq1E4Rq5ONvGteRLeiFDjWRKLcm4_6=25dSOcGtsmAcO4KWSg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 611 bytes --]
On Fri, Jan 18, 2013 at 05:00:34PM +0100, David Herrmann wrote:
[...]
> Also ${} is pretty standard in makefiles, isn't it?
The curly braces are allowed and valid syntax, but I haven't seen many
uses of them. Historically only $() was a documented feature, while ${}
was accepted as equivalent but undocumented. Apparently ${} is more
common on BSD or in older makefiles. According to Wikipedia[0], the ${}
variant is "rarely used". While Wikipedia isn't necessarily an
authoritative source, it certainly corresponds with my experience in
this case.
Thierry
[0]: http://en.wikipedia.org/wiki/Make_(software)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2013-01-21 6:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 12:22 [PATCH] man: Fix typo and use $() for make expressions Thierry Reding
2013-01-18 16:00 ` David Herrmann
2013-01-18 16:01 ` David Herrmann
2013-01-18 16:54 ` Jesse Barnes
2013-01-25 15:54 ` David Herrmann
2013-01-25 21:47 ` Jesse Barnes
2013-01-20 6:39 ` Mark Zhang
2013-01-20 9:17 ` David Herrmann
2013-01-20 9:41 ` Mark Zhang
2013-01-21 6:52 ` Thierry Reding [this message]
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=20130121065254.GA15508@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=dh.herrmann@googlemail.com \
--cc=dri-devel@lists.freedesktop.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 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.