From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH eutils] Introduce run_in_build_dir() used in a few ebuilds.
Date: Mon, 14 Jan 2013 11:41:46 -0800 [thread overview]
Message-ID: <CAAr7Pr9wO-BN2ncsJPxWsv4ox3aG9Hdp70vyK14Ru9e2TnV7Kw@mail.gmail.com> (raw)
In-Reply-To: <19130161.GGbXe2B6Je@smorgbox>
On Mon, Jan 14, 2013 at 9:30 AM, Dan Douglas <ormaaj@gmail.com> wrote:
> On Sunday, January 13, 2013 06:02:26 PM Michał Górny wrote:
>> On Sun, 13 Jan 2013 07:36:59 -0800
>> Alec Warner <antarus@gentoo.org> wrote:
>> > local -i ret
>> > ?
>>
>> Looks good. I didn't even know bash has something like that.
>>
>
> Useless use of -i is usually unhelpful. In Bash (but not all shells), it's
> slower, because it's still just storing the value as a string and marking the
> variable with the integer attribute which modifies the way certain assignments
> behave.
>
> It doesn't do any harm in this specific case, but there are a lot of gotchas
> with -i to be aware of if you're going to use it.
> --
> Dan Douglas
It is bash...there are lots of gotchas with almost *all* of bash's features ;)
-A
next prev parent reply other threads:[~2013-01-14 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 13:29 [gentoo-dev] [PATCH eutils] Introduce run_in_build_dir() used in a few ebuilds Michał Górny
2013-01-13 15:05 ` William Hubbs
2013-01-13 15:08 ` Michał Górny
2013-01-13 15:43 ` Gilles Dartiguelongue
2013-01-13 15:52 ` William Hubbs
2013-01-13 17:01 ` Michał Górny
2013-01-13 17:18 ` Gilles Dartiguelongue
2013-01-13 15:36 ` Alec Warner
2013-01-13 17:02 ` Michał Górny
2013-01-14 17:30 ` Dan Douglas
2013-01-14 19:41 ` Alec Warner [this message]
2013-01-13 18:28 ` Mike Frysinger
2013-01-14 17:55 ` Dan Douglas
2013-01-14 22:09 ` Mike Frysinger
2013-01-15 3:20 ` [gentoo-dev] " Duncan
2013-01-15 5:03 ` Dan Douglas
2013-01-15 19:46 ` Mike Frysinger
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=CAAr7Pr9wO-BN2ncsJPxWsv4ox3aG9Hdp70vyK14Ru9e2TnV7Kw@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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