On 8/22/21 7:52 PM, Kerin Millar wrote:
On Sun, 22 Aug 2021 16:13:28 -0400
Chet Ramey wrote:
On 8/21/21 1:28 AM, Emanuele Torre wrote:
Bash Version: 5.1
Patch Level: 8
Release Status: release
get_epochrealtime() casts tv.tv_sec (a time_t a.k.a. int) to unsigned
int causing EPOCHREALTIME
On Sun, 22 Aug 2021 16:13:28 -0400
Chet Ramey wrote:
> On 8/21/21 1:28 AM, Emanuele Torre wrote:
>
> > Bash Version: 5.1
> > Patch Level: 8
> > Release Status: release
> >
>
> > get_epochrealtime() casts tv.tv_sec (a time_t a.k.a. int) to unsigned
> > int causing EPOCHREALTIME to not behave co
lol undefined behavior, tho its important to test such important
functionality, as setting time back
bad book by the live of 'use your computer only so'
im just saying nowadays as earlier software is more ugly bugs than useful
On Sun, Aug 22, 2021, 23:28 Greg Wooledge wrote:
> On Sun, Aug 22,
On Sun, Aug 22, 2021 at 10:30:26PM +0200, Alex fxmbsw7 Ratchev wrote:
> why disregard or invalid, mark 0 is that date, less is minus, .. all working
It's not that simple. Calendars get really *interesting* if you go
farther back in history. The switch from the Julian to the Gregorian
calendar di
why disregard or invalid, mark 0 is that date, less is minus, .. all working
On Sun, Aug 22, 2021, 22:13 Chet Ramey wrote:
> On 8/21/21 1:28 AM, Emanuele Torre wrote:
>
> > Bash Version: 5.1
> > Patch Level: 8
> > Release Status: release
> >
>
> > get_epochrealtime() casts tv.tv_sec (a time_t a.
On 8/21/21 1:28 AM, Emanuele Torre wrote:
Bash Version: 5.1
Patch Level: 8
Release Status: release
get_epochrealtime() casts tv.tv_sec (a time_t a.k.a. int) to unsigned
int causing EPOCHREALTIME to not behave correctly before the Unix Epoch.
The definition is seconds since the Unix epoch.
Date:Sat, 21 Aug 2021 07:28:23 +0200
From:Emanuele Torre
Message-ID:
| I have also read that gettimeofday() is considered obsolete and is
| deprecated by POSIX.
It is being removed as a required interface, but it still exists
everywhere (and will for a very lon