[EMAIL PROTECTED] (Chris Devers) writes:
> On Fri, 29 Oct 2004, Jenda Krynicky wrote:
>
> > Actually no. They are generaly not very fast. The reason is that the
> > shell interpreter needs to create a new process for each and every
> > commend you specify in the script [...]
>
> Is this true even for built in shell commands? For example, commands
> like cd, echo, export, kill, test, etc are all built in to Bash -- does
> an external process run whenever you invoke one of these?
No, that's why they're called shell builtins. That functionality was
so common, that it was added into popular shell programs precisely to
save the cost of an exec() call.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Lawrence Statton - [EMAIL PROTECTED] s/aba/c/g
Computer software consists of only two components: ones and
zeros, in roughly equal proportions. All that is required is to
sort them into the correct order.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
