[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Support for sub-second time in decoded time
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Support for sub-second time in decoded time |
|
Date: |
Mon, 29 Jul 2019 17:23:51 +0300 |
> From: Lars Ingebrigtsen <address@hidden>
> Date: Mon, 29 Jul 2019 11:48:02 +0200
>
> `current-time' returns its data as (HIGH LOW USEC PSEC), but now that we
> have bignum support, perhaps we don't need to do it this way. What
> about just having a field in decoded times that's the fraction of a
> second?
That'd be backward-incompatible, no?
- Re: Support for sub-second time in decoded time, (continued)
- encode-time vs decode-time, Stefan Monnier, 2019/07/29
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/07/30
- Re: encode-time vs decode-time, Andy Moreton, 2019/07/30
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/07/30
- Re: encode-time vs decode-time, Paul Eggert, 2019/07/30
- Re: encode-time vs decode-time, Paul Eggert, 2019/07/30
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/07/31
- Re: encode-time vs decode-time, Stefan Monnier, 2019/07/31
Re: Support for sub-second time in decoded time,
Eli Zaretskii <=
Re: Support for sub-second time in decoded time, Paul Eggert, 2019/07/29