Re: time(1): perror(3) -> err(3) and friends

Few weeks bump. Any feedback on this fabulous Scott Cheloha/ingo@ collaboration? Slightly re-tweaked patch below; while here: kill(getpid(), sig) -> raise(sig) I didn't even know there was a raise(3) function until this weekend, they really did think of everything. -- Scott Cheloha

Re: time(1): perror(3) -> err(3) and friends

> On Jul 22, 2017, at 12:49 PM, Ingo Schwarze wrote: > > [...] > > * In main(), prefer "return" over exit(3). Any particular reason for this or is that just the style that people have settled on? And to be clear you're saying warn("whatever"); return 1; is

Re: time(1): perror(3) -> err(3) and friends

Hi, Scott Cheloha wrote on Thu, Jul 13, 2017 at 07:30:26PM -0500: > We currently use a mix of perror(3) and err(3). > > In one case you can merge perror + exit into err, which is nice. > > The warns, though, are not equivalent (you get a "time: " prefix), > so maybe this is too risky. > >

time(1): perror(3) -> err(3) and friends

We currently use a mix of perror(3) and err(3). In one case you can merge perror + exit into err, which is nice. The warns, though, are not equivalent (you get a "time: " prefix), so maybe this is too risky. Putting it out here anyway. -- Scott Cheloha Index: usr.bin/time/time.c