Robert Elz dixit: > | This specifically means that builtins MAY be made available > | to exec, and that thatb s an expected modus operandi. > >It means nothing of the kind. The System Interfaces volume of POSIX.1-2008 >is the part that defines the system calls.
There’s no “exec” system call, so that’s the wrong part you’re searching in for this. >What the text you quoted is saying (if you had quoted it all) is that >all of the built-in utilities (except the special built-ins) must be >able to be accessed by execle(2) (and its sibling interfaces.) > >Note not may, must. Yes, that *too*, but it also says that they *may* be builtins. >Aside from the possibility that the sh exec special-builtin might be >intended to make an exec*() system call (the spec does not say that) Note that the exec built-in utility does not need to perfom an exec*() system call. > | Heck, you can exec a function! > >That is where we started. That is, that is the question. Can you? Of course you do, see the definition of “command” near the top of the shell section. bye, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour”
