Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: bug with for and time

X-seq: zsh-workers 20457
From: Dan Nelson <dnelson@xxxxxxxxxxxxxxx>
To: "Matthias B." <msbREMOVE-THIS@xxxxxxxxxxxxxxx>
Subject: Re: bug with for and time
Date: Tue, 5 Oct 2004 13:18:20 -0500
Cc: zsh-workers@xxxxxxxxxx
In-reply-to: <20041005113848.6f3715bd@xxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <41616CDC.8020701@xxxxxxxxxxxxxxxx> <200410041610.i94GAl92005952@xxxxxxxxxxxxxx> <20041005113848.6f3715bd@xxxxxxxxxxxxxxxxxxxxx>

In the last episode (Oct 05), Matthias B. said:
> On Mon, 04 Oct 2004 17:10:47 +0100 Peter Stephenson <pws@xxxxxxx> 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.

-- 
	Dan Nelson
	dnelson@xxxxxxxxxxxxxxx

Follow-Ups:
- Re: bug with for and time
  - From: Matthias B.

References:
- bug with for and time
  - From: Nathan Sidwell
- Re: bug with for and time
  - From: Peter Stephenson
- Re: bug with for and time
  - From: Matthias B.

Messages sorted by: Reverse Date, Date, Thread, Author