Why "print" is not bound to a PATH element... / was: Re:[ksh93-integration-discuss] ksh93 update 2 [PSARC/2009/063FastTrack timeout02/09/2009]

[Roland Mainz]

James Carlson wrote:
> Roland Mainz writes:
> > 2. Restricted shell scripts (e.g. "rsh", "rksh", "pfrksh" [2] etc.) need
> > a way to output data (e.g. counterpart to "read") and therefore "print"
> > was never bound to a PATH element since the korn shell exists. Otherwise
> > you have shell scripts which can't output anything except syntax errors
> > when running in "restricted" shell mode.
> 
> OK; that's the key bit I was looking for.  "print" is a built-in even
> when $PATH doesn't have a "print" on it, and binding would break that.

Right (BTW: the same applies to "printf" and "sleep") ...

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)