From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from localhost by hawkwind.utcs.toronto.edu with SMTP id <2223>; Fri, 21 May 1993 15:05:04 -0400
Return-Path: techfak.uni-bielefeld.de!malte
Received: from techfac.TechFak.Uni-Bielefeld.DE ([129.70.132.100]) by hawkwind.utcs.toronto.edu with SMTP id <2685>; Fri, 21 May 1993 09:24:17 -0400
Received: from idefix.TechFak.Uni-Bielefeld.DE
	by techfac.TechFak.Uni-Bielefeld.DE id AA27685; Fri, 21 May 1993 15:23:52 +0200
Received: by idefix.techfak.uni-bielefeld.de (5.0/tp.29.0890)
	id AA27027; Fri, 21 May 93 15:23:50 +0200
Date:	Fri, 21 May 1993 09:23:50 -0400
From:	malte@TechFak.Uni-Bielefeld.DE
Message-Id: <9305211323.AA27027@idefix.techfak.uni-bielefeld.de>
To:	rc-owner
Subject: builtin time
Resent-To: rc
Resent-Date: Fri, 21 May 1993 15:04:50 -0400
Resent-From: Chris Siebenmann <cks>
Resent-Message-Id: <93May21.150504edt.2223@hawkwind.utcs.toronto.edu>

I hardly dare to ask for it, but what about a "time" builtin ? I'm well
aware of the existance of /usr/bin/time or whereever it may reside, but
that doesn't allow to measure the time it took a builtin or a function
to complete.

I came across this when I tried to measure the time it takes for several
commands running in parallel,
like

	for( i in *.c ){ cc $i & } ; time wait $apids

which, of course, gives only an approximization. The correct way is

	{ for( i in *.c ){ time cc $i & }} | sed -f filter.script

measure each cc run independently and sum up the outputs.

Any opinions about it ?

Malte