From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: efficiency
Date: Sat, 04 Feb 2017 08:38:52 -0800 [thread overview]
Message-ID: <63db3cdf-833e-d5b5-b519-2c9eeeeb595c@eastlink.ca> (raw)
In-Reply-To: <20170204154736.5a51b119@ntlworld.com>
On 04/02/17 07:47 AM, Peter Stephenson wrote:
>
> I'm sure this has come up before, but if you're in a position where a
> saving of this kind is important, there's a good chance you shouldn't
> really be using a shell at all.
Of course. Still it's good to understand the theory of the thing. As I
said, in practice the difference was a milisecond but I backed the wrong
horse, which is instructive since it suggests that the shell likes fewer
lines more than it likes simplified calculation. Just curious. In
practice I'll always go for robustness and better code style.
next prev parent reply other threads:[~2017-02-04 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 2:55 efficiency Ray Andrews
2017-02-04 15:05 ` efficiency Peter Stephenson
2017-02-04 15:39 ` efficiency Ray Andrews
2017-02-04 15:47 ` efficiency Peter Stephenson
2017-02-04 16:38 ` Ray Andrews [this message]
2017-02-04 16:47 ` efficiency Peter Stephenson
2017-02-04 17:39 ` efficiency Ray Andrews
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=63db3cdf-833e-d5b5-b519-2c9eeeeb595c@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).