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

[James Carlson]

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.

Thanks.

+1

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677