Re: status update
Sam Steingold <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
> * Jan Stary <[email protected]> [2016-08-30 11:10:34 +0200]: > > More importantly, /bin/pwd is a standardized UNIX binary, > guaranteed to exist, with behaviour defined by POSIX > - as opposed to "pwd", which can be a shell builtin > (of whichever shell the user is running), > or anything named "pwd" that happens to be in $PATH. Excellent! Indeed, the _functionality_ is specified: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/pwd.html http://pubs.opengroup.org/onlinepubs/9699919799/utilities/cat.html Note, however, that /bin is not mentioned in http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap10.html I agree that the UNIX tradition enshrines /bin sufficiently so that we need not worry that /bin/pwd or /bin/cat will ever surprise us: https://en.wikipedia.org/wiki/Unix_filesystem https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard http://www.linfo.org/bin.html http://unix.stackexchange.com/questions/5915/difference-between-bin-and-usr-bin http://askubuntu.com/questions/138547/how-to-understand-the-ubuntu-file-system-layout The bottom line is that there is no compelling case to drop the full path, so let us keep it for the time being. -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1404 http://www.childpsy.net/ http://iris.org.il http://jihadwatch.org http://truepeace.org http://islamexposedonline.com http://palestinefacts.org C combines the power of assembler with the portability of assembler. ------------------------------------------------------------------------------ _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel