From: Mikael Magnusson <mikachu@gmail.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: zsh/datetime $EPOCHREALTIME
Date: Wed, 10 Aug 2011 18:13:31 +0200 [thread overview]
Message-ID: <CAHYJk3SZrN4OO_aX5Biv5wozsTMuDfz2aapXSnN=VN3Ob60UAA@mail.gmail.com> (raw)
In-Reply-To: <110810090819.ZM4843@torch.brasslantern.com>
On 10 August 2011 18:08, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Aug 10, 4:41pm, Peter Stephenson wrote:
> }
> } On Wed, 10 Aug 2011 08:30:17 -0700
> } Bart Schaefer <schaefer@brasslantern.com> wrote:
> } > Allow the user to apply typeset to EPOCHSECONDS. If it's an int,
> } > it is as it is now. If it's a float, what you called EPOCHREALTIME.
> } > If an array, elements for seconds and nanoseconds. If a hash, the
> } > keys are tv_sec and tv_nsec like a timespec (convert from tv_usec
> } > when using gettimeofday).
> }
> } That's the trick I did with SECONDS, but a utility library like
> } zsh/datetime might be called in lots of different places and
> } come a cropper if the type is wrong (e.g. supplying a float to
> } strftime screws up), so I thought it would be better to minimise the
> } assumptions needed.
>
> Good point regarding overloading EPOCHSECONDS. So, introduce a new
> variable EPOCHTIMESPEC (or just EPOCHTIME, I suppose).
>
> Regarding Mikael's question ... is there any way for the getfn of an
> array to know what array element has been accessed? E.g. could the
> function update the time only when the entire array or the first
> (seconds) element is accessed, and return the previous value when
> the nanoseconds is accessed?
>
> If not, he's right, you'd always have to copy it (which is probably
> not a big deal if you're already interested in each bit separately).
>
> for sec nsec in $EPOCHTIME; do ...
Also, since we're dealing with nanoseconds it's nice if we don't spend
too many cycles mucking about, I know that is quite an optimistic
statement when talking about zsh, but still ;).
--
Mikael Magnusson
prev parent reply other threads:[~2011-08-10 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 11:21 Peter Stephenson
2011-08-10 11:37 ` Mikael Magnusson
2011-08-10 11:41 ` Peter Stephenson
2011-08-10 15:30 ` Bart Schaefer
2011-08-10 15:38 ` Mikael Magnusson
2011-08-10 16:19 ` Peter Stephenson
2011-08-11 18:33 ` Peter Stephenson
2011-08-10 15:41 ` Peter Stephenson
2011-08-10 16:08 ` Bart Schaefer
2011-08-10 16:13 ` Mikael Magnusson [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='CAHYJk3SZrN4OO_aX5Biv5wozsTMuDfz2aapXSnN=VN3Ob60UAA@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=zsh-workers@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).