Alan Hargreaves writes:
> Unlike other built-in commands named in PSARC/2006/550, the "print"
> built-in in ksh93 will _not_ be bound to the /usr/bin/ pathname to
> ensure backwards-compatiblity to existing ksh93 scripts (for example
> scripts running in "restricted" shell mode expect that some shell
> builtins are available independently from the value of ${PATH}).Could someone on the ksh93 team explain this bit in a little more detail? It might be just a nit, but I don't follow the logic above: what usage case requires that this path isn't bound? -- 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
