zsh-workers
 help / color / mirror / code / Atom feed
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 17:38:52 +0200	[thread overview]
Message-ID: <CAHYJk3T4K2kpRqdbYV6na-1brS66BzbDwzuWgpn-wBiTpng7-A@mail.gmail.com> (raw)
In-Reply-To: <110810083017.ZM4722@torch.brasslantern.com>

On 10 August 2011 17:30, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Aug 10, 12:41pm, Peter Stephenson wrote:
> }
> } I'm actually wondering if we ought to be a bit smarter and add an
> } epochrealtime array with the seconds and nanoseconds as elements
> } (guaranteed to be consistent, obviously). Exercise for the reader.
>
> Better (?) still:
>
> 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).
>
> Too bad that would require mucking about with whether it's special
> and readonly, or else introducing provision for other special cases
> into typeset ...

If it's an array, how do you get both elements at the 'same' time? I'm
guessing you would always have to copy the array in one step and then
access the elements in the copy.

-- 
Mikael Magnusson


  reply	other threads:[~2011-08-10 15:39 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 [this message]
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

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=CAHYJk3T4K2kpRqdbYV6na-1brS66BzbDwzuWgpn-wBiTpng7-A@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).