Re: bug with for and time

["Matthias B." <msbREMOVE-THIS@winterdrache.de>]

On Tue, 5 Oct 2004 13:18:20 -0500 Dan Nelson <dnelson@allantgroup.com>
wrote:

> In the last episode (Oct 05), Matthias B. said:
> > On Mon, 04 Oct 2004 17:10:47 +0100 Peter Stephenson <pws@csr.com>
> > wrote:
> > > Nathan Sidwell wrote:
> > > > Zsh 4.0.4 appears to lose the time command in the following,
> > > > 
> > > > nathan@garibaldi:363>for i in 1 2 ; time echo
> > > > 
> > > > but, place the command in a subshell, and it works.
> > > 
> > > Yes, that's always been an annoying limitation: "time" works by
> > > gettings system information about subprocesses, and there isn't one
> > > in this case.
> > 
> > Then how does bash do it? bash can time builtins just fine.
> 
> It probably calls getrusage(RUSAGE_SELF) before and after whatever
> you're timing, then prints the deltas.

Then maybe zsh should do that, too. Right now, zsh's time function doesn't
work very well. Look at this:

/home/msb> TIMEFMT=$'real\t%*Es\nuser\t%*Us\nsys \t%*Ss\ncpu \t%P'
/home/msb> time /bin/echo foo
foo
real    0.000s
user    0.000s
sys     0.010s
cpu     8695%
/home/msb> time /bin/echo foo
foo
real    0.006s
user    0.000s
sys     0.000s
cpu     0%
/home/msb> time /bin/echo foo
foo
real    0.000s
user    0.010s
sys     0.000s
cpu     8928%


The numbers don't add up properly. I've never seen something like this
with bash.

MSB

-- 
Happiness through ignorance!