From: Ray Andrews <rayandrews@eastlink.ca>
To: Zsh Users <zsh-users@zsh.org>
Subject: efficiency
Date: Fri, 03 Feb 2017 18:55:53 -0800 [thread overview]
Message-ID: <b6cf1ad2-056f-c093-fef8-74c995ee6dbd@eastlink.ca> (raw)
Gentlemen:
echo "\nSTOP TIMER. REAL RUNTIME: $((now-start)) MILISECONDS
($(((now-start)/60000)):${(l:2::0:)$(((now-start)/1000%60))}) $@"
integer -x base=$(((now-start)/1000))
echo "\nSTOP TIMER. REAL RUNTIME: $((now-start)) MILISECONDS
($(($base/60)):${(l:2::0:)$(($base%60))}) $@"
... is there any real advantage to the second line? Obviously I'm
trying to cut down on duplicate calculation, and in the real world it
hardly matters, but as a point of principal, which is better?
next reply other threads:[~2017-02-04 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 2:55 Ray Andrews [this message]
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 ` efficiency Ray Andrews
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=b6cf1ad2-056f-c093-fef8-74c995ee6dbd@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).