* Re: builtin time
@ 1993-05-21 19:13 Paul Haahr
0 siblings, 0 replies; 2+ messages in thread
From: Paul Haahr @ 1993-05-21 19:13 UTC (permalink / raw)
To: malte; +Cc: rc
for just this reason (inability to time builtins, in a shell where
more things look like builtins), we added time to es.
paul
^ permalink raw reply [flat|nested] 2+ messages in thread
* builtin time
@ 1993-05-21 13:23 malte
0 siblings, 0 replies; 2+ messages in thread
From: malte @ 1993-05-21 13:23 UTC (permalink / raw)
To: rc-owner
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1993-05-21 19:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1993-05-21 19:13 builtin time Paul Haahr
-- strict thread matches above, loose matches on Subject: below --
1993-05-21 13:23 malte
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).