Hi! ----
We've noticed some issues with the "whence" builtin in ast-ksh.2013-04-09 when a builtin is bound to multiple paths. Example: -- snip -- $ ~/bin/ksh -x -c 'builtin cmp ; export PATH=/usr/ast/bin:/usr/bin:/bin ; builtin | fgrep cmp ; whence -a cmp ; true' + builtin cmp + PATH=/usr/ast/bin:/usr/bin:/bin + export PATH + fgrep cmp + builtin /bin/cmp /usr/ast/bin/cmp cmp + whence -a cmp cmp is a shell builtin cmp is a shell builtin version of /usr/ast/bin/cmp cmp is /usr/bin/cmp cmp is an undefined function + true -- snip -- Questions: 1. Why is there an inconsistency between the output of "whence -a cmp" for "/usr/bin/cmp" and "/usr/ast/bin/cmp" ? Is this because builtins in /usr/ast/bin (or /opt/ast/bin in AST's default configuration) are executed even if the matching file in the file system does not exist (in any case this should IMO be documented in the "whence" man page) ? 2. What does "cmp is an undefined function" mean ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [email protected] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
