Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Compile fix for 64-bit HPUX
Date: Thu, 30 Mar 2006 13:05:00 -0000	[thread overview]
Message-ID: <jeu09g6z4r.fsf@sykes.suse.de> (raw)
In-Reply-To: <20060329230151.GC9916@nevyn.them.org> (Daniel Jacobowitz's 	message of "Wed, 29 Mar 2006 18:01:51 -0500")

Daniel Jacobowitz <drow@false.org> writes:

> On Wed, Mar 29, 2006 at 01:13:15AM +0200, Andreas Schwab wrote:
>> Daniel Jacobowitz <drow@false.org> writes:
>> 
>> >> +    oldcflags="${CFLAGS-}"
>> >
>> > What's ${foo-}?  I don't see it in my bash or dash docs.
>> 
>> In (bash)Shell Parameter Expansion, the paragraph before the table:
>> 
>>        When not performing substring expansion, Bash tests for a parameter
>>     that is unset or null; omitting the colon results in a test only for a
>>                            ^^^^^^^^^^^^^^^^^^
>>     parameter that is unset.
>
> Thanks.  I see this in the dash documentation too, and pdksh, so it is
> presumably portable.

The autoconf manual says:

`${VAR:-VALUE}'
     Old BSD shells, including the Ultrix `sh', don't accept the colon
     for any shell substitution, and complain and die.

Thus in fact, omitting the colon is more portable.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2006-03-30  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 10:16 Randolph Chung
2006-03-28 22:27 ` Daniel Jacobowitz
2006-03-29  0:18   ` Andreas Schwab
2006-03-30  0:05     ` Daniel Jacobowitz
2006-03-30 13:05       ` Andreas Schwab [this message]
2006-03-30 13:37         ` Randolph Chung

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=jeu09g6z4r.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb-patches@sourceware.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