>>>>> On 30 Jan 2002 09:26:52 -0500 >>>>> "Paul" == Paul Smith <Paul> wrote: Paul> Paul> %% Alexander Kotelnikov <[EMAIL PROTECTED]> writes: ak> LIE. Read standards, please. Paul> Paul> Single UNIX says: Paul> Paul> If the process image file is not a valid executable object, execlp() Paul> and execvp() use the contents of that file as standard input to a Paul> command interpreter conforming to system(). In this case, the Paul> command interpreter becomes the new process image. Paul> ak> are execlp and execvp all exec's you know? Paul> Paul> For heaven's sake. The standard doesn't say that _only_ these exec's Paul> must work that way, it says _at least_ these exec's must work that way. Paul> Paul> I've been using UNIX systems of various flavors for 17+ years and I Paul> can't remember _ever_ using one that didn't handle this properly (where Paul> if you invoked a script from a shell and the script didn't have a legal Paul> "#!" interpreter line, it wasn't given to sh).
You are about "this works", and I am about "this is wrong". Shell is not the one program who exec. Paul> The current code works, and works everywhere it's been tried. If you Paul> have a situation where it doesn't work, file a bug. If you just don't Paul> like the way it looks, get over it. Damn, I do. Before distributing fvwm24_convert in debian fvwm package I add #! line. BTW just tried to execl'ed and failed with "Exec format error". -- Alexander Kotelnikov Saint-Petersburg, Russia -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
